On what platform? Here's what I use for Windows:

bjam.exe --toolset=msvc address-model=64 --stagedir=./stage64release --build-dir=./build64release --layout=system --without-mpi variant=release link=shared threading=multi runtime-link=shared install --prefix=./win64release/indep --exec-prefix=./win64release/bin --libdir=./win64release/lib --includedir=./win64release/include
bjam.exe --toolset=msvc address-model=64 --stagedir=./stage64debug --build-dir=./build64debug --layout=system --without-mpi variant=debug link=shared threading=multi runtime-link=shared install --prefix=./win64debug/indep --exec-prefix=./win64debug/bin --libdir=./win64debug/lib --includedir=./win64debug/include

Note that "address-model=64" doesn't have a "--" prefix. This bites lots of people (including me...) You need to run these in a Visual Studio 64-bit command prompt. It's similar for Linux, --toolset=gcc and from memory OSX is --toolset=darwin.

Damien

On 02/07/2010 11:33 PM, Sean Farrow wrote:

Hi:

I am currently in the process of writing an application that uses boost that needs to be compilable under x64. Do I have to recompile boost using bjam, if so how do I do this for x64 platforms?

Cheers

Sean.
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users