Re: [boost] How do I use bjam?

From: Deane Yang (deane_yang_at_[hidden])
Date: 2006-01-05 23:14:02

Daryle Walker wrote:
> Following another response, I created a "~/boost-build.jam" file with:
> 
> //========================================================================
> boost-build ~/Documents/Programming/Boost/main-cvs/boost/tools/build/v2 ;
> //========================================================================
> 
> as its only line...

Oops. I forgot to mention that the path should be relative to the 
directory that the file boost-build.jam is in.

[After Daryle figures this out himself]
> daryle[doc]$ bjam
> Jamfile: No such file or directory
> Jamfile: No such file or directory
> ..found 8 targets...
> daryle[doc]$ bjam --v2
> error: Boost.Jam version 3.1.12 or later required
> 
> //========================================================================
> 
> At least I'm closer than before....
> 

Yes, you are. And I got this same error message, too. Unfortunately, I 
don't remember how I resolved this.

But I suggest looking at:
http://www.boost.org/doc/html/bbv2/installation.html
and
http://www.boost.org/tools/build/jam_src/index.html#building_bjam

In particular, I recommend downloading the latest from the CVS 
repository and building bjam from scratch. Do "bjam --version" to test 
whether you've got things set up OK.

I recommend downloading the PDF version of the Boost Build V2 
documentation and keep looking through it. It's a little disorganized, 
but if you keep reading it, you eventually find almost everything you 
need. For the rest, there's the boost.build mailing list.

Also, make sure you edit user-config.jam properly.

But keep trying! It is well worth the effort. Once you figure out bjam, 
you can suddenly compile your libraries on different platforms 
effortlessly using the exact same setup and sequence of commands. All 
the headaches with figuring out the right linker and linker options to 
use for each platform just disappear (because someone smarter than me 
has figured it all out and configured bjam to do the right thing).