Hello,

I've had a few problems over the years running the build for boost.
The command line I use is:

vs2010

b2 toolset=msvc-10.0 --stagedir=stage\x32 variant=debug,release threading=multi link=static runtime-link=static --with-date_time --with-thread --with-system --with-chrono --with-atomic stage

vs2013

b2 toolset=msvc-12.0 --stagedir=stage\x32 variant=debug,release threading=multi link=static runtime-link=static --with-date_time --with-thread --with-system --with-chrono --with-atomic stage

vs2015

b2 toolset=msvc-14.0 --stagedir=stage\x32 variant=debug,release threading=multi link=static runtime-link=static --with-date_time --with-thread --with-system --with-chrono --with-atomic stage


64 bit

using the 64 bit visual-studio command prompt run the following command in the boost directory 

vs2010

b2 toolset=msvc-10.0 --stagedir=stage\x64 address-model=64 variant=debug,release threading=multi link=static runtime-link=static --with-date_time --with-thread --with-system --with-chrono --with-atomic stage

vs2013

b2 toolset=msvc-12.0 --stagedir=stage\x64 address-model=64 variant=debug,release threading=multi link=static runtime-link=static --with-date_time --with-thread --with-system --with-chrono --with-atomic stage

vs2015

b2 toolset=msvc-14.0 --stagedir=stage\x64 address-model=64 variant=debug,release threading=multi link=static runtime-link=static --with-date_time --with-thread --with-system --with-chrono --with-atomic stage

When the task is completed the 64bit libraries will be found in <boostDIR>\stage\lib\x64\lib

These commands are broken down as follows:
toolset=msvc-14.0

The version of visual studio-compile to use.

 --stagedir=stage\x64

The output directory for the lib-files

 address-model=64

This is used to instruct B2 to compile 64-bit libraries

 variant=debug,release

This will instruct B2 to build both the release and debug libs

 threading=multi

Used to instruct boost to use multi-threading - I'd recommend using it unless you are building a single-threaded software

 link=static 

Static output Lib files (rather than DLLs)

runtime-link=static

Outputs the static-libraries, rather than dynamic libraries with static-wrappers

 --with-date_time --with-thread --with-system --with-chrono --with-atomic stage

Using the --with-library instructs B2 to only build these specific libraries.
If you know exactly what libraries you want to compile this can save you hours of compile time. If you don't know what you need, omit this - it will build everything.


On 13 February 2015 at 19:09, 許 善閎 <iscream.frank@hotmail.com> wrote:
I am trying boost_1_57 on Windows 8_1. I have downloaded the prebuilt msvc boost library. Now I want to use tdm-gcc to recompiled it, but when I saw the output files, the name of debug version library file only with flag d on it, not like the prebuilt boost library I downloaded, the filenames are with flag g and d on them. I've already tried several combinations of options and properties like the command below:
b2 --build-dir=D:\tmp --stagedir=. toolset=gcc address-model=32 variant=debug runtime-debugging=on cxxflags="-g3 -DDebug=1 -D_GLIBCXX_DEBUG" stage
But the library files I got,  of which names are still only d flag on them.
I've learned programming for some days, but I know not much things about "make" "rule" etc.
Could anyone tell me how to do? 
Thank you!  : )

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build