Win7 Compile Boost Library summary

In many cases, the boost library will be used, but it may be possible to download the compiled binary library directly from Boostpro, but unfortunately it is no longer available at this time.

The following is a manual compilation of the process instructions, version 1.44 as an example to illustrate;

The first step, executing Bootstrap.bat, will generate Bjam.exe in the same directory. The subsequent compilation will depend on the Bjam.exe

Note: Bjam.exe--show-libraries can see the names of the libraries that can be compiled, select them as appropriate, or compile them all, but it will take a long time, it is recommended to compile the

Step two, start compiling
Bjam.exe toolset=msvc-10.0--build-type=complete address-model=64--with-serialization--with-system--with-date_ Time--with-regex--with-filesystem--

Stagedir= "E:\try\boost_1_44_0\lib64" stage

Or

Bjam.exe toolset=msvc-10.0--build-type=complete address-model=64--with-serialization--with-system--with-date_ Time--with-regex--with-filesystem--

prefix= "E:\try\boost_1_44_0\lib64" Install

Description: Previously only serialization/system/date_time/regex/filesystem five libraries were compiled

Note:
Stage/install:stage means that only the libraries (DLLs and Lib) are generated, the generated files are placed on the subdirectory of the stage, the path is specified by the parameter--stagedir, and the install also generates an include directory containing the header files, the resulting file

The record is specified by the parameter--prefix

Address-model: Generate 32/64-bit libraries, do not use the default, generate 32-bit library files to generate 64-bit libraries to display the specified address-model=64

Toolset: Specifies the compiler for C + + [VS2008 corresponds to--toolset=msvc-9.0,vs2010--toolset=msvc-10.0], others can find relevant reference notes

--build-type: Compile type, what kind of library to generate, release/debug version, etc., it is recommended to choose Complete, build the debug version and release version, but the time required for a little longer

Link: Create a dynamic [link=shared] or static [link=static] library.

Runtime-link: Specifies whether the C + + runtime library is a static [runtime-link=static] link or a dynamic [runtime-link=shared] Link

Threading: Single [Threading=single]/multithreaded [Threading=multi] compiled.

Without/with: Choose not to compile/compile which libraries

Bjam Some common parameters
--build-dir=<builddir>    compiled temporary files will be placed in the BuildDir (this is better management, compile it can delete it)
-- stagedir=<stagedir>    Store the path to the compiled library file, which is the default stage
--build-type=complete    Compile all versions, or only a small subset of the versions will be compiled (exactly equivalent to: Variant=release, threading=multi;link=shared|static;runtime-link=shared)
variant=debug|release    decide what version to compile (debug or release?) The
link=static|shared    determines whether to use a static library or a dynamic library. The
threading=single|multi    determines whether to use a single-threaded or multi-line libraries. The
runtime-link=static|shared    determines whether to statically or dynamically link a C/S standard library.
--with-<library>    compiles only the specified libraries, such as input--with-regex, and compiles only the Regex library.
--show-libraries    Displays the library names that need to be compiled