Index
The most reliable way to get a copy of Boost is to download a distribution from SourceForge:
The first thing many people want to know is, “how do I build Boost?” The good news is that often, there's nothing to build.
To keep things simple, let's start by using a header-only library. The following program reads a sequence of integers from standard input, uses Boost.Lambda to multiply each number by three, and @@ -240,7 +240,7 @@ echo 1 2 3 | ./example
Don't be alarmed if you see compiler warnings originating in Boost
headers. We try to eliminate them, but doing so isn't always
practical.3 Errors are another matter. If you're
@@ -253,11 +253,11 @@ correctly identified the
- If you want to use any of the separately-compiled Boost libraries,
you'll need to acquire library binaries. Issue the following commands in the shell (don't type $; that
represents the shell's prompt): If you're using a compiler other than your system's default, you'll
need to use Boost.Build to create binaries. You'll also
use this method if you need a nonstandard build variant (see the
@@ -298,7 +298,7 @@ installing software. To use it, you'll need an executable called
bjam. bjam is the command-line tool that drives the Boost Build
system. To build Boost binaries, you'll invoke bjam from the
Boost root. First, find the toolset corresponding to your compiler in the
-following table. Note If you previously chose a toolset for the purposes of
@@ -382,10 +383,6 @@ operating system.
Boost.Build will place all intermediate files it generates while
building into the build directory. If your Boost root
directory is writable, this step isn't strictly necessary: by
@@ -420,16 +417,18 @@ default Boost.Build will create a
Change your current directory to the Boost root directory and
invoke bjam as follows: For a complete description of these and other invocation options,
+please see the Boost.Build documentation. For example, your session might look like this: That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “--build-type=complete”. During the process of building Boost libraries, you can expect to
see some messages printed on the console. These may include The only error messages you see when building Boost—if any—should
be related to the IOStreams library's support of zip and bzip2
formats as described here. Install the relevant development
@@ -498,17 +497,16 @@ packages for libz and libbz2 if you need those features. Other
errors when building Boost libraries are cause for concern. If it seems like the build system can't find your compiler and/or
linker, consider setting up a user-config.jam file as described
-in the Boost.Build documentation. If that isn't your problem or
-the user-config.jam file doesn't work for you, please address
-questions about configuring Boost for your compiler to the
-Boost.Build mailing list. To demonstrate linking with a Boost binary library, we'll use the
following simple program that extracts the subject lines from
emails. It uses the Boost.Regex library, which has a
@@ -548,7 +546,7 @@ $ c++ -I path/to/boost_1
~/boost/lib/libboost_regex-gcc34-mt-d-1_36.a
- You can separately specify a directory to search (with -Ldirectory) and a library name to search for (with -llibrary,2 dropping the filename's leading lib and trailing
+ You can separately specify a directory to search (with -Ldirectory) and a library name to search for (with -llibrary,2 dropping the filename's leading lib and trailing
suffix (.a in this case): In both cases above, the bold text is what you'd add to the
command lines we explored earlier. To test our subject extraction, we'll filter the following text
file. Copy it out of your browser and save it as jayne.txt: This concludes your introduction to Boost and to integrating it
with your programs. As you start using Boost in earnest, there are
surely a few additional points you'll wish we had covered. One day
@@ -735,7 +733,7 @@ to the
5 Prepare to Use a Boost Library Binary
+5 Prepare to Use a Boost Library Binary
5.1 Easy Build and Install
+5.1 Easy Build and Install
@@ -285,7 +285,7 @@ path in place of the Boost root directory.
5.2 Or, Build Custom Binaries
+5.2 Or, Build Custom Binaries
5.2.1 Get bjam
+5.2.1 Get bjam
5.2.2 Identify Your Toolset
+5.2.2 Identify Your Toolset
Intel
-kylix
-Borland
-
-msvc
Microsoft
@@ -412,7 +409,7 @@ a hyphen, e.g. intel-9.0borland-5.4.3.
5.2.3 Select a Build Directory
+5.2.3 Select a Build Directory
5.2.4 Invoke bjam
+5.2.4 Invoke bjam
-bjam --build-dir=build-directory --toolset=toolset-name stage
+bjam --build-dir=build-directory toolset=toolset-name stage
+
$ cd ~/boost_1_39_0
-$ bjam --build-dir=/tmp/build-boost --toolset=gcc stage
+$ bjam --build-dir=/tmp/build-boost toolset=gcc stage
5.3 Expected Build Output
+5.3 Expected Build Output
@@ -490,7 +489,7 @@ look something like:
5.4 In Case of Build Errors
+5.4 In Case of Build Errors
6 Link Your Program to a Boost Library
+6 Link Your Program to a Boost Library
$ c++ -I path/to/boost_1_39_0 example.cpp -o example \
@@ -566,7 +564,7 @@ automatically for you unless you pass a special option such as
6.1 Library Naming
+6.1 Library Naming
@@ -581,7 +579,7 @@ following elements:
using a special debug build of Python.
d
-building a debug version of your code.5
+building a debug version of your code.5
p
using the STLPort standard library rather than the default one supplied with
your compiler.
n
-using STLPort's deprecated “native iostreams” feature.6
+using STLPort's deprecated “native iostreams” feature.6
6.2 Test Your Program
+6.2 Test Your Program
@@ -698,7 +696,7 @@ Spoil Rock Hunter?”
7 Conclusion and Further Resources
+7 Conclusion and Further Resources
[2] That option is a dash followed by a lowercase “L”
+ [2] That option is a dash followed by a lowercase “L”
character, which looks very much like a numeral 1 in some fonts.