Click here to Skip to main content
Click here to Skip to main content

Building Boost libraries for Visual Studio

, 18 Jul 2007
Rate this:
Please Sign up or sign in to vote.
Building boost libraries for Visual Studio


The Boost initiative is the next hottest thing after STL for the C++ community. While the documentation is quite good, it can be overwhelming to get a quick start. This simple article explains a method of building Boost libraries. I wrote it because many questions in the newsgroups are about linker errors, which happen if you try to link against some of the Boost libraries. The original article was written with Boost version 1.33, but the updated version works only with the new Bjam syntax which was introduced with version 1.34.


While most of the Boost libraries are template-based, some of them - e.g. date-time, regex, filesystem, signals - come with CPP source files and thus require actual code to be generated. Boost uses a build system called Bjam, which can be configured for a lot of platforms. I work only on Windows with Visual Studio 2003, I'll describe here a configuration for this combination. At work though, we already use Visual Studio 2008.

Building Boost

After downloading the Boost libraries and unpacking them in a folder - referenced in this article with <boost_root>, e.g. on my PC it is C:\work sdk\boost, the libraries need to be built:

  1. Build Bjam
  2. Build the Boost libraries

Building Bjam

Bjam can be built in two ways:

  • Use the 'bootstrap.bat' batch file located in <boost_root>. Run this batch file and Bjam will be automatically built and added to the root.
  • Build Bjam 'manually': browse to <boost_root>\tools\build\jam_src and run build.bat from a command prompt. This will start to build Bjam, which ends up in <boost_root>\tools\build\jam_src\bin.ntx86\bjam.exe. Copy this file to the root of Boost, <boost_root>.

Building Boost Libraries

The Bjam system must be told that you want to build debug/release libraries, build with threading in mind, and link against various options of the STL or platforms. I only use Visual Studio with Plauger's STL, but use two different versions of Visual Studio:

  1. Build a debug build with multithreading and dynamic linking for VC++ 7.1.
  2. Build a release build with multithreading and dynamic linking for VC++ 7.1.
  3. Build a debug build with multithreading and dynamic linking for VC++ 9.0.
  4. Build a release build with multithreading and dynamic linking for VC++ 9.0.

With the release of Visual Studio 2005 / 2008, Microsoft supports side by side installations of the crt. With manifests, one can bind a module to a specific version of the crt. The Boost libraries are dependent on the crt as well, and you can instruct the build process to use the latest version through a '_BIND_TO_CURRENT_VCLIBS_VERSION' define. This leads to the following options for Visual Studio 2003 / 2008:

  1. bjam toolset=msvc-7.1 variant=debug threading=multi link=shared
  2. bjam toolset=msvc-7.1 variant=release threading=multi link=shared
  3. bjam toolset=msvc-9.0 variant=debug threading=multi link=shared define=_BIND_TO_CURRENT_VCLIBS_VERSION
  4. bjam toolset=msvc-9.0 variant=release threading=multi link=shared define=_BIND_TO_CURRENT_VCLIBS_VERSION

I've already made four batch files with the same command(s):

Copy these batch files to the root of Boost, <boost_root>. Now the libraries can be built:

  1. Open the command prompt.
  2. Run vcvars32.bat from Visual Studio.
  3. Run the batch files, e.g. zbuilddebug_vc71.bat.

Bjam will now try to build the libraries.

Building All

For the stressful software engineer, I offer here two batch files which will do it all together: they build bjam if it does not exist and build the debug and release mode libraries in one go:

After the build process has finished, the library executables are created in the <boost_root>\bin.v2 directory, e.g.:

  • boost_date_time-vc71-mt-gd-1_41.dll for the multithreaded debug build of a date-time library.
  • boost_date_time-vc71-mt-1_41.dll for the multithreaded release build of a date-time library.

Because all of these files are built under their own library names, one can copy them all - i.e. search on 'mt-gd-1_41 and mt-1_41 - to one location and adjust Visual Studio to point to this library location. Alternatively one can use the <boost_root>\stage directory. However this directory does not contain the associated PDBs, which is unhandy during debugging.

Using Boost Libraries

We have built the shared libraries and therefore we have to instruct Visual Studio to link against them. Fortunately, Boost has incorporated an "autolink" feature. Thus, with the preprocessor one can link to the correct libraries. Define the following preprocessor statements:


Even better, include a header file in your precompiled header before including a Boost header:

Room for Improvement

  • For some reason, the "normal," i.e. non-dynamic, libraries get built.
  • Python library should also get built, but for some reason it gets excluded.
  • Visual Studio 2005 introduces the safe C and iterator concepts. Boost libraries don't like them and should be turned off.


  • 11 September, 2005 - Original version posted
  • 18 July, 2007 - Updated with Boost 1.34 syntax
  • 25 November 2009 - Updated with manifests and the 'all' batch file; removed old syntax


  • Leon Wiertz: tip about manifests and the 'all' batch file


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Software Developer (Senior)
Netherlands Netherlands
Born in the Netherlands in 1971. Spent since 1998 years as a software engineer programming Windows application(s) using, UML, C++, MFC, STL, DirectShow and Boost.

Comments and Discussions

GeneralLife saver Pinmemberogrig20-Apr-06 18:29 
GeneralVS 2003 PinmemberAnthony_Yio14-Feb-06 15:32 
GeneralRe: VS 2003 PinmemberFlying_oe2-Mar-06 14:22 
GeneralSome refinements PinmemberNetCE13-Feb-06 11:21 
Here is the build string I personally use to build Boost. This works for me with 1.33.1 on vc 7.1 and 8.0.
First of all, it is a good idea to thoroughly read through Boost Getting Started[^].
I downloaded the prebuilt bjam.exe from SourceForge and stuck it in the Boost root folder. Saves a step and less CDing.
Change directory to the Boost root folder, and then:
bjam "-sBUILD=debug <runtime-link>dynamic <threading>multi" -sTOOLS=vc-8_0 --stagedir=. --with-python-version=2.4 --with-python-root=../Python-2.4.2 --with-pydebug stage
Notice I'm only building the multithread debug dll versions. If you want all versions, you can eliminate the -sBUILD parameter altogether.
Staging. I don't like the default locations Boost.Build puts stuff, so I tell it to "stage" to the root directory. This means it copies the build libs to the specified location. Since it always stages into a "lib" subfolder, this has the effect of putting the libs into <boost-root>/lib
If you want boost.python, Python needs to be built already, before you start building Boost. Boost needs the Python import libs. Notice the various --with-python* parameters above. You really need to tell Boost where your Python build is. It will try the defaults but you may get surprising results. I strongly recommend downloading the Python source and doing your own build, so the debug stuff can work properly. Note that I am using relative paths; I put all my third-party libs in one place. Your setup may vary.
I don't think there is a way to specify only static or dll versions of libs, since not all libs support both. This may change in Build v2.
-- modified at 17:23 Monday 13th February, 2006
GeneralRe: Some refinements Pinmemberoleg635-Oct-07 10:51 
GeneralRe: Some refinements PinmemberChetan Sheladiya2-Nov-09 23:02 
QuestionVC2005 PinmemberEd K18-Dec-05 17:31 
AnswerRe: VC2005 PinmemberGast12819-Dec-05 8:08 
AnswerRe: VC2005 Pinmemberloadcom5-May-07 0:51 
GeneralRe: VC2005 Pinmemberoleg635-Oct-07 10:28 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web04 | 2.8.140721.1 | Last Updated 18 Jul 2007
Article Copyright 2005 by Gast128
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid