Re: [Boost-users] MinGW Build Issues

On Jan 15, 2008 10:01 PM, Jonathan Turkanis wrote:

Chris Miller wrote:

...

On Jan 15, 2008 9:17 PM, Jonathan Turkanis wrote:

...

Chris Miller wrote:

...

Why on earth I try and support Windows is beyond my comprehension. It's just something I do.

I'm having some massive difficulties making Boost build with MinGW so I can start using it from Code::Blocks. I've tried using Boost's native Jam system, but first I have to build that. You don't have to build it; you can download a pre-built binary: http://tinyurl.com/2q36f.

For MinGW/Windows Vista, which one would I pick?

I assume boost-jam-3.1.16-1-ntx86.zip

Oh, silly me. NT x86... I keep forgetting I'm using a NT kernel. Microsoft and their weird naming systems. I think it's wiser for me to learn how to build it from source, however. What if I run into binary compatibility issues after a GCC upgrade? I know it's probably not an issue, but I also want to make the build setup process harder as a project leader to try and filter out the faint of heart. The moment you say "game" in a programming forum there are many people interested, but very rarely do you find someone with the drive to see it through.

...

I picked the "platform independent" one, which didn't work.

Needless to say, the platform independent download is not one of the pre-built binaries.

...

...

...

Any help here would be nice! Have you tried:

set PATH= build mingw

?

That's not what the build instructions said. They said to use build.bat mingw, 'cause that's my toolkit. It kept trying it with MSVC for some odd reason.

It shouldn't matter which toolset you use to build bjam. The resulting executable will still work with MinGW.

I thought it was only C that had a binary layout contract or whatever they call it. That's cool, though off topic, how does that work?

If you read Building Bjam (http://www.boost.org/doc/html/jam/building.html), you will see that running

bjam <toolset-name>

requires that the compiler be in your PATH. In addition, I've found that having other compilers in my PATH sometimes confuses build.bat.

I just enforced that PATH variable after my last shutdown. I'm at school and on my Kubuntu laptop now, but when I get home this is going to be one of my first things after homework. Should I add MSYS to the PATH as well, or do you think that will be necessary? I have MSYS installed, I'm just not sure. I don't have MSVC installed, nor have I ever had it installed on this OS, so I wonder why it picked MSVC. Wait a sec... maybe because it wasn't exported to the PATH it didn't apply in the batch file? So next boot it should work? Perhaps. It'll be interesting to write that down on the wiki... Thanks for the help! -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman John 3:16! If Microsoft is the Wal*Mart of the Software World, then Linux is the Home Depot