Index
+The most reliable way to get a copy of Boost is to download a -distribution from SourceForge:
+distribution from SourceForge:Download boost_1_82_0.tar.bz2.
+Download boost_1_93_0.tar.bz2.
In the directory where you want to put the Boost installation, execute
-tar --bzip2 -xf /path/to/boost_1_82_0.tar.bz2 +tar --bzip2 -xf /path/to/boost_1_93_0.tar.bz2
This is a sketch of the resulting directory structure:
-boost_1_82_0/ .................The “boost root directory”
+boost_1_93_0/ .................The “boost root directory”
index.htm .........A copy of www.boost.org starts here
boost/ .........................All Boost Header files
`` ``
@@ -136,7 +136,7 @@ anything you can use in these directories.
It's important to note the following:
The path to the boost root directory (often /usr/local/boost_1_82_0) is +
The path to the boost root directory (often /usr/local/boost_1_93_0) is sometimes referred to as $BOOST_ROOT in documentation and mailing lists .
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 @@ -244,7 +244,7 @@ int main()
Now, in the directory where you saved example.cpp, issue the following command:
-c++ -I path/to/boost_1_82_0 example.cpp -o example +c++ -I path/to/boost_1_93_0 example.cpp -o example
To test the result, type:
@@ -254,10 +254,10 @@ echo 1 2 3 | ./example-4.1 Errors and Warnings
+4.1 Errors and Warnings
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 +practical.3 Errors are another matter. If you're seeing compilation errors at this point in the tutorial, check to be sure you've copied the example program correctly and that you've correctly identified the Boost root directory.
@@ -267,15 +267,15 @@ correctly identified the -5 Prepare to Use a Boost Library Binary
+5 Prepare to Use a Boost Library Binary
If you want to use any of the separately-compiled Boost libraries, you'll need to acquire library binaries.
-5.1 Easy Build and Install
+5.1 Easy Build and Install
Issue the following commands in the shell (don't type $; that represents the shell's prompt):
-$ cd path/to/boost_1_82_0 +$ cd path/to/boost_1_93_0 $ ./bootstrap.sh --helpSelect your configuration options and invoke ./bootstrap.sh again @@ -299,7 +299,7 @@ path in place of the Boost root directory.
-5.2 Or, Build Custom Binaries
+5.2 Or, Build Custom Binaries
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 @@ -309,7 +309,7 @@ use this method if you need a nonstandard build variant (see the
-5.2.1 Install Boost.Build
+5.2.1 Install Boost.Build
Boost.Build is a text-based system for developing, testing, and installing software. First, you'll need to build and install it. To do this:
@@ -322,7 +322,7 @@ the directory where you want Boost.Build to be installed-5.2.2 Identify Your Toolset
+5.2.2 Identify Your Toolset
First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).
@@ -406,7 +406,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
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 @@ -414,17 +414,17 @@ default Boost.Build will create a bin.v2/ subd purpose in your current working directory.
-5.2.4 Invoke b2
+5.2.4 Invoke b2
Change your current directory to the Boost root directory and invoke b2 as follows:
-b2 --build-dir=build-directory toolset=toolset-name `` `` stage +b2 --build-dir=build-directory toolset=toolset-name `` `` stageFor a complete description of these and other invocation options, please see the Boost.Build documentation.
For example, your session might look like this:
-$ cd ~/boost_1_82_0 +$ cd ~/boost_1_93_0 $ b2 --build-dir=/tmp/build-boost toolset=gcc stageThat will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “--build-type=complete”.
@@ -463,7 +463,7 @@ file by appending “>build.log -5.3 Expected Build Output
+5.3 Expected Build Output
During the process of building Boost libraries, you can expect to see some messages printed on the console. These may include
@@ -487,7 +487,7 @@ look something like:
-5.4 In Case of Build Errors
+5.4 In Case of Build Errors
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 @@ -504,7 +504,7 @@ for your compiler to the -
6 Link Your Program to a Boost Library
+6 Link Your Program to a Boost Library
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 @@ -540,14 +540,14 @@ project.
- -
You can specify the full path to each library:
-$ c++ -I path/to/boost_1_82_0 example.cpp -o example \ +$ c++ -I path/to/boost_1_93_0 example.cpp -o example \ ~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.aYou 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):
-$ c++ -I path/to/boost_1_82_0 example.cpp -o example \ +$ c++ -I path/to/boost_1_93_0 example.cpp -o example \ -L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36As you can see, this method is just as terse as method A for one @@ -562,7 +562,7 @@ automatically for you unless you pass a special option such as
In both cases above, the bold text is what you'd add to the command lines we explored earlier.
-6.1 Library Naming
+6.1 Library Naming
@@ -577,7 +577,7 @@ following elements:- Prefix: except on Microsoft Windows, every Boost library name begins with this string. On Windows, only ordinary static libraries use the lib prefix; import libraries and DLLs do -not.4
+not.4- boost_regex
- Library name: all boost library filenames begin with boost_.
- -vc71
@@ -620,7 +620,7 @@ libraries.python-debugging=on d -building a debug version of your code.5 +building a debug version of your code.5 variant=debug p @@ -728,7 +728,7 @@ version number, will also be created.-6.2 Test Your Program
+6.2 Test Your Program
To test our subject extraction, we'll filter the following text file. Copy it out of your browser and save it as jayne.txt:
@@ -768,7 +768,7 @@ Spoil Rock Hunter?”-7 Conclusion and Further Resources
+7 Conclusion and Further Resources
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 @@ -793,7 +793,7 @@ mailing list.
@@ -812,7 +812,7 @@ character, which looks very much like a numeral 1 in some fonts.
- [1] If developers of Boost packages would like to work + @@ -802,7 +802,7 @@ to the [1] If developers of Boost packages would like to work with us to make sure these instructions can be used with their packages, we'd be glad to help. Please make your interest known to the Boost developers' list. - [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.