Building boost for VS2005 SP1 & VS 2008

Hi, I would like to build boost library in 2 configurations (as mentioned below) for my project. 1. Visual Studio 2005 SP1 2. Visual Studio 2008 Also I want to use is on 32bit windows XP and also on 64 bit. So I guess I need it with above 2 configurations (VS2005 SP1 & 2008) both on 32 bit and 64 bit machine. Please confirm. I am using below version - Version 1.35.0 Boost Jam 3.1.16 I am following below steps to build on VS 2005 - * Unzip "boost-jam-3.1.16.zip" and run "build.bat" - As a result "bjam.exe" is created in folder "boost-jam-3.1.16\bin.ntx86" * Unzip "boost_1_35_0.zip" in say "C:\Boost" folder * Copy "bjam.exe" to "C:\Boost\boost_1_35_0" path * Go to command prompt and make current directory as "C:\Boost\boost_1_35_0" * Run the command below (For Microsoft Visual C++ command-line tools from Visual Studio .NET 2005) to build boost bjam "-sTOOLS=vc-8_0" install Regards, Mukund

Ambardekar, Mukund wrote:
* Run the command below (For Microsoft Visual C++ command-line tools from Visual Studio .NET 2005) to build boost
bjam "-sTOOLS=vc-8_0" install
Are you following the getting started instructions? http://www.boost.org/doc/libs/1_35_0/more/getting_started/windows.html#invok... -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

I'm not an expert but I've been down part of this path and kept notes. You have to use architecture=x86/address-model=%z/stagedir=stage%z Where %z is 32 or 64. Then copy the staged libraries into library folders with names differing by Win32 versus x64; then you can use the Visual Studio build-in macro $(PlatformName) in your project files or Tools/Options library path settings to select the right folder. You're on your own to extend this to two versions of Studio. If you don't specify the architecture and address model I've seen problems with intermediate folders being shared between 32- and 64-bit builds, breaking one or both. You may want to call for a full rebuild anyway to get around the issue. My notes call for specifying -a -d0, release or debug, and stage as well. Good luck. Release and Debug use different filenames, as do the various combinations of link and runtime-link options, so you can do all of those builds into the same stage folder.
participants (3)
-
Ambardekar, Mukund
-
Rene Rivera
-
Stephen Nuchia