From aa169994b7ba3dec3900742f436d203f04f26329 Mon Sep 17 00:00:00 2001 From: Beman Dawes Date: Mon, 11 May 2009 01:08:45 +0000 Subject: [PATCH] Prep for 1.40.0 [SVN r52888] --- getting_started/detail/release-variables.rst | 6 +- getting_started/unix-variants.html | 258 +++++++------- getting_started/windows.html | 339 ++++++++++--------- 3 files changed, 302 insertions(+), 301 deletions(-) diff --git a/getting_started/detail/release-variables.rst b/getting_started/detail/release-variables.rst index 3f7fe8f..f14f5d4 100644 --- a/getting_started/detail/release-variables.rst +++ b/getting_started/detail/release-variables.rst @@ -5,8 +5,8 @@ .. This file contains all the definitions that need to be updated .. for each new release of Boost. -.. |boost-version-number| replace:: 1.39.0 -.. |boost_ver| replace:: ``boost_1_39_0`` -.. |boost_ver-bold| replace:: **boost_1_39_0** +.. |boost-version-number| replace:: 1.40.0 +.. |boost_ver| replace:: ``boost_1_40_0`` +.. |boost_ver-bold| replace:: **boost_1_40_0** .. _sf-download: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041 diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html index 2baff48..42086e6 100644 --- a/getting_started/unix-variants.html +++ b/getting_started/unix-variants.html @@ -3,14 +3,15 @@ - + Boost Getting Started on Unix Variants
-

Getting Started on Unix Variants

+

Getting Started on Unix Variants

+ @@ -26,48 +27,48 @@ .. _`Getting Started on Windows`: windows.html .. _Cygwin: http://www.cygwin.com .. _MinGW: http://mingw.org --> -
-

Index

+ -
-

1   Get Boost

+
+

1   Get Boost

The most reliable way to get a copy of Boost is to download a -distribution from SourceForge:

+distribution from SourceForge:

    -

  1. Download boost_1_39_0.tar.bz2.

    +

  2. Download boost_1_40_0.tar.bz2.

  3. In the directory where you want to put the Boost installation, execute

    -tar --bzip2 -xf /path/to/boost_1_39_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_40_0.tar.bz2
@@ -78,19 +79,19 @@ library packages, however you may need to adapt these instructions if you use third-party packages, because their creators usually choose to break Boost up into several packages, reorganize the directory structure of the Boost distribution, -and/or rename the library binaries.1 If you have +and/or rename the library binaries.1 If you have any trouble, we suggest using an official Boost distribution -from SourceForge.

+from SourceForge.

-
-

2   The Boost Distribution

+
+

2   The Boost Distribution

This is a sketch of the resulting directory structure:

-boost_1_39_0/ .................The “boost root directory”
+boost_1_40_0/ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost/ .........................All Boost Header files
     
@@ -122,7 +123,7 @@ the Python library's def.hpp
 
  • Some libraries have an “aggregate header” in boost/ that
 #includes all of the library's other headers.  For
-example, Boost.Python's aggregate header is
    
+example, Boost.Python's aggregate header is
    
 
     boost/python.hpp.
 
    
@@ -135,7 +136,7 @@ anything you can use in these directories.

    • It's important to note the following:

      -

    1. The path to the boost root directory (often /usr/local/boost_1_39_0) is +

    2. The path to the boost root directory (often /usr/local/boost_1_40_0) is sometimes referred to as $BOOST_ROOT in documentation and mailing lists .

      3. @@ -164,8 +165,8 @@ contains a subset of the Boost documentation. Start with
    -
    -

    3   Header-Only Libraries

    +
    +

    3   Header-Only Libraries

    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.

    @@ -178,26 +179,26 @@ treatment when linking.

    The only Boost libraries that must be built separately are:

    A few libraries have optional separately-compiled binaries:

      -
    • Boost.DateTime has a binary component that is only needed if +
    • Boost.DateTime has a binary component that is only needed if you're using its to_string/from_string or serialization features, or if you're targeting Visual C++ 6.x or Borland.
      • -
    • Boost.Graph also has a binary component that is only needed if -you intend to parse GraphViz files.
      • -
    • Boost.Test can be used in “header-only” or “separately compiled” +
    • Boost.Graph also has a binary component that is only needed if +you intend to parse GraphViz files.
      • +
    • Boost.Test can be used in “header-only” or “separately compiled” mode, although separate compilation is recommended for serious use.
    @@ -205,8 +206,8 @@ use.
    -
    -

    4   Build a Simple Program Using Boost

    +
    +

    4   Build a Simple Program Using Boost

    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 @@ -230,7 +231,7 @@ int main()

    Now, in the directory where you saved example.cpp, issue the following command:

    -c++ -I path/to/boost_1_39_0 example.cpp -o example
+c++ -I path/to/boost_1_40_0 example.cpp -o example

    To test the result, type:

    @@ -239,29 +240,29 @@ 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.
    
+be sure you've copied the example program correctly and that you've
+correctly identified the Boost root directory.
    
 
 
 
 
    
 
    
-
    
-
    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_39_0
+$ cd path/to/boost_1_40_0
 $ ./bootstrap.sh --help
 
    
 
    Select your configuration options and invoke ./bootstrap.sh again
@@ -282,42 +283,42 @@ installation prefix.  You will also find a copy of the Boost
 headers in the include/ subdirectory of the installation
 prefix, so you can henceforth use that directory as an #include
 path in place of the Boost root directory.
    
-
    skip to the next step
    
+
    skip to the next step
    
 
    
-
    
-
    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
+need to use Boost.Build to create binaries.  You'll also
 use this method if you need a nonstandard build variant (see the
-Boost.Build documentation for more details).
    
+Boost.Build documentation for more details).
    
 
 
 
-
    Boost.Build is a text-based system for developing, testing, and
+
    Boost.Build is a text-based system for developing, testing, and
 installing software.  To use it, you'll need an executable called
 bjam.
    
 
-
    
-
    5.2.1   Get bjam
    
+
    
+
    5.2.1   Get 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.
    
-
    We suggest you download a pre-built bjam executable for your platform.
-Alternatively, you can build bjam yourself using these
+
    We suggest you download a pre-built bjam executable for your platform.
+Alternatively, you can build bjam yourself using these
 instructions.
    
 
    Move the bjam executable into a directory in your PATH.  You can
 see the list of directories in your PATH, separated by colons,
 by typing “echo $PATH” at the command prompt.
    
 
    
-
    
-
    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
+following table (an up-to-date list is always available in the
 Boost.Build documentation).
    
 
    
 
    Note
    
 
    If you previously chose a toolset for the purposes of
-building bjam, you should assume it won't work and instead
+building bjam, you should assume it won't work and instead
 choose newly from the table below.
    
 
    
 
@@ -346,7 +347,7 @@ known to work well with Boost
@@ -408,34 +409,34 @@ you can append the version number to the toolset name, preceded by
 a hyphen, e.g. intel-9.0 or
 borland-5.4.3.  
    
-
    
-
    5.2.3   Select a Build Directory
    
-
    Boost.Build will place all intermediate files it generates while
+
    
+
    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
 default Boost.Build will create a bin.v2/ subdirectory for that
 purpose in your current working directory.
    
 
    
-
    
-
    5.2.4   Invoke bjam
    
+
    
+
    5.2.4   Invoke bjam
    
 
    Change your current directory to the Boost root directory and
 invoke bjam as follows:
    
 
    -bjam --build-dir=build-directory toolset=toolset-name   stage
+bjam --build-dir=build-directory toolset=toolset-name   stage
 
    
 
    For a complete description of these and other invocation options,
-please see the Boost.Build documentation.
    
+please see the Boost.Build documentation.
    
 
    For example, your session might look like this:
    
 
    -$ cd ~/boost_1_39_0
+$ cd ~/boost_1_40_0
 $ bjam --build-dir=/tmp/build-boost toolset=gcc stage
 
    
-
    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``”.
    
+
    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”.
    
 
 
 
 
    Building the special stage target places Boost
-library binaries in the stage/lib/ subdirectory of your build
+library binaries in the stage/lib/ subdirectory of your build
 directory.
    
 
    
 
    Note
    
@@ -460,12 +461,12 @@ be interested in:
    
 
    Boost.Build can produce a great deal of output, which can
 make it easy to miss problems.  If you want to make sure
 everything is went well, you might redirect the output into a
-file by appending “``>build.log 2>&1``” to your command line.
    
+file by appending “>build.log 2>&1” to your command line.
    
 
    
 
    
 
    
-
    
-
    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
    
 
      
@@ -488,28 +489,28 @@ 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
+formats as described here.  Install the relevant development
 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
-here.  If that isn't your problem or the user-config.jam file
+here.  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.
    
+for your compiler to the Boost.Build mailing list.
    
 
 
 
 
    
 
    
-
    
-
    6   Link Your Program to a Boost Library
    
+
    
-
+
-
+
-
+
    
 
    como
 Comeau Computing
 Using this toolset may
-require configuring another
+require configuring another
 toolset to act as its backend
 
    
 
    cw
 using debug versions of the standard and runtime support libraries.
 
    
 
    yusing a special debug build of Python.using a special debug build of Python.
 
    
 
    dbuilding a debug version of your code.5building a debug version of your code.5
 
    
 
    p
 using the STLPort standard library rather than the default one supplied with
 your compiler.
 
    
 
    nusing STLPort's deprecated “native iostreams” feature.6using STLPort's deprecated “native iostreams” feature.6
 
    
     
 
    
@@ -655,8 +656,8 @@ 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:
    
 
    @@ -695,23 +696,23 @@ 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
 we may have a “Book 2 in the Getting Started series” that addresses
 them.  Until then, we suggest you pursue the following resources.
 If you can't find what you need, or there's anything we can do to
-make this document clearer, please post it to the Boost Users'
+make this document clearer, please post it to the Boost Users'
 mailing list.
    
 
 
    
 
    Onward
    
@@ -724,17 +725,16 @@ mailing list.
    
 
-
+to the Boost developers' list.
    
 
 
    [1]
    If developers of Boost packages would like to work
+
    [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.
    
     
 
    
@@ -744,7 +744,7 @@ character, which looks very much like a numeral 1 in some fonts.
 
-
    
 
 
    [3]Remember that warnings are specific to each compiler
+
    [3]Remember that warnings are specific to each compiler
 implementation.  The developer of a given Boost library might
 not have access to your compiler.  Also, some warnings are
 extremely difficult to eliminate in generic code, to the point
@@ -755,7 +755,7 @@ have any source code mechanism for suppressing warnings.
    
 
    
-
@@ -764,7 +764,7 @@ same name.
    
 
 
    [4]This convention distinguishes the static version of
+
    [4]This convention distinguishes the static version of
 a Boost library from the import library for an
 identically-configured Boost DLL, which would otherwise have the
 same name.
    
 
    
-
    
 
 
    [5]These libraries were compiled without optimization
+
    [5]These libraries were compiled without optimization
 or inlining, with full debug symbols enabled, and without
 NDEBUG #defined.  Although it's true that sometimes
 these choices don't affect binary compatibility with other
@@ -774,7 +774,7 @@ compiled code, you can't count on that with Boost libraries.
    
 
    
-
diff --git a/getting_started/windows.html b/getting_started/windows.html
index 9087dcc..4bfd2a5 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -3,86 +3,87 @@
 
-
+Boost Getting Started on Windows
    
-
     Getting Started on Windows
    
+
     Getting Started on Windows
    
+
 
 
 
 
    
-
    A note to Cygwin and MinGW users
    
+
    A note to Cygwin and MinGW users
    
 
    If you plan to use your tools from the Windows command prompt,
-you're in the right place.  If you plan to build from the Cygwin
+you're in the right place.  If you plan to build from the Cygwin
 bash shell, you're actually running on a POSIX platform and
-should follow the instructions for getting started on Unix
-variants.  Other command shells, such as MinGW's MSYS, are
+should follow the instructions for getting started on Unix
+variants.  Other command shells, such as MinGW's MSYS, are
 not supported—they may or may not work.
    
 
    
-
    
-
    Index
    
+
    
+
    Index
    
 
    
-
    
-
    1   Get Boost
    
+
    
+
    1   Get Boost
    
 
    The easiest way to get a copy of Boost is to use an installer.  The
-Boost website version of this Getting Started guide will have
+Boost website version of this Getting Started guide will have
 undated information on installers as they become available, or see
-Boost downloads or the installer provided by BoostPro
+Boost downloads or the installer provided by BoostPro
 Computing.  We especially recommend using an installer if you use
 Microsoft Visual Studio, because the installer can download and
 install precompiled library binaries, saving you the trouble of
 building them yourself.  To complete this tutorial, you'll need to at
-least install the Static Multithreaded variants of the Boost.Regex
+least install the Static Multithreaded variants of the Boost.Regex
 binaries when given the option.
    
 
    If you're using an earlier version of Visual Studio or some other
 compiler, or if you prefer to build everything yourself, you can
-download boost_1_39_0.7z or boost_1_39_0.zip and unpack it to install a complete Boost
-distribution.1
    
+download boost_1_40_0.7z or boost_1_40_0.zip and unpack it to install a complete Boost
+distribution.1
    
 
 
 
 
    
-
    
-
    2   The Boost Distribution
    
+
    
+
    2   The Boost Distribution
    
 
    This is a sketch of the resulting directory structure:
    
 
    -boost_1_39_0\ .................The “boost root directory”
+boost_1_40_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -114,7 +115,7 @@ the Python library's def.hpp
 
  • Some libraries have an “aggregate header” in boost\ that
 #includes all of the library's other headers.  For
-example, Boost.Python's aggregate header is
    
+example, Boost.Python's aggregate header is
    
 
     boost\python.hpp.
 
    
@@ -127,7 +128,7 @@ anything you can use in these directories.
    
 
    • 
 
    It's important to note the following:
    
 
      
-
    1. The path to the boost root directory (often C:\Program Files\boost\boost_1_39_0) is
+
    2. The path to the boost root directory (often C:\Program Files\boost\boost_1_40_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
      
 
      3. 
@@ -161,8 +162,8 @@ contains a subset of the Boost documentation.  Start with
 
 
 
    
-
    
-
    3   Header-Only Libraries
    
+
    
+
    3   Header-Only Libraries
    
 
    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.
    
 
    
@@ -175,26 +176,26 @@ treatment when linking.
    
 
 
    The only Boost libraries that must be built separately are:
    
 
 
    A few libraries have optional separately-compiled binaries:
    
 
      
-
    • Boost.DateTime has a binary component that is only needed if
+
    • Boost.DateTime has a binary component that is only needed if
 you're using its to_string/from_string or serialization
 features, or if you're targeting Visual C++ 6.x or Borland.
      • 
-
    • Boost.Graph also has a binary component that is only needed if
-you intend to parse GraphViz files.
      • 
-
    • Boost.Test can be used in “header-only” or “separately compiled”
+
    • Boost.Graph also has a binary component that is only needed if
+you intend to parse GraphViz files.
      • 
+
    • Boost.Test can be used in “header-only” or “separately compiled”
 mode, although separate compilation is recommended for serious
 use.
      • 
 
    
@@ -202,8 +203,8 @@ use.
 
 
 
    
-
    
-
    4   Build a Simple Program Using Boost
    
+
    
+
    4   Build a Simple Program Using Boost
    
 
    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
@@ -224,11 +225,11 @@ int main()
 }
 
 
    Copy the text of this program into a file called example.cpp.
    
-
    
-
    Note
    
+
    
+
    Note
    
 
    To build the examples in this guide, you can use an
 Integrated Development Environment (IDE) like Visual Studio, or
-you can issue commands from the command prompt.  Since every
+you can issue commands from the command prompt.  Since every
 IDE and compiler has different options and Microsoft's are by
 far the dominant compilers on Windows, we only give specific
 directions here for Visual Studio 2005 and .NET 2003 IDEs and
@@ -252,14 +253,14 @@ cd path\to\some\directory
 
 
    followed by Return.  For example,
    
 
    -cd C:\Program Files\boost\boost_1_39_0
+cd C:\Program Files\boost\boost_1_40_0
 
    
 
    Long commands can be continued across several lines by typing a
 caret (^) at the end of all but the last line.  Some examples
 on this page use that technique to save horizontal space.
    
 
    
-
    
-
    4.1   Build From the Visual Studio IDE
    
+
    
+
    4.1   Build From the Visual Studio IDE
    
 
      
 
    • From Visual Studio's File menu, select New > Project…
      
 
      • 
@@ -277,12 +278,12 @@ select Properties from the resulting pop-up menu
      
 
    • In Configuration Properties > C/C++ > General > Additional Include
 Directories, enter the path to the Boost root directory, for example
      
 
      
-
      C:\Program Files\boost\boost_1_39_0
      
+
      C:\Program Files\boost\boost_1_40_0
      
 
      
 
      • 
 
    • In Configuration Properties > C/C++ > Precompiled Headers, change
 Use Precompiled Header (/Yu) to Not Using Precompiled
-Headers.3
      
+Headers.3
      
 
      • 
 
    • Replace the contents of the example.cpp generated by the IDE
 with the example code above.
      
@@ -297,10 +298,10 @@ into the resulting window, followed by the Return key:
      
 
 
      Then hold down the control key and press "Z", followed by the
 Return key.
      
-
      skip to the next step
      
+
      skip to the next step
      
 
    
-
    
-
    4.2   Or, Build From the Command Prompt
    
+
    
+
    4.2   Or, Build From the Command Prompt
    
 
    From your computer's Start menu, if you are a Visual
 Studio 2005 user, select
    
 
    
@@ -310,12 +311,12 @@ Studio 2005 user, select
    
 
    
 All Programs > Microsoft Visual Studio .NET 2003
 > Visual Studio .NET Tools > Visual Studio .NET 2003 Command Prompt
    
-
    to bring up a special command prompt window set up for the
-Visual Studio compiler.  In that window, set the current
+
    to bring up a special command prompt window set up for the
+Visual Studio compiler.  In that window, set the current
 directory to a suitable location for creating some temporary
 files and type the following command followed by the Return key:
    
 
    -cl /EHsc /I path\to\boost_1_39_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_40_0 path\to\example.cpp
 
    
 
    To test the result, type:
    
 
    @@ -325,35 +326,35 @@ echo 1 2 3 | example
 
 
 
    
-
    
-
    4.3   Errors and Warnings
    
+
    
+
    4.3   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.5 Errors are another matter.  If you're
+practical.5 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.
    
+be sure you've copied the example program correctly and that you've
+correctly identified the Boost root directory.
    
 
 
 
 
    
 
    
-
    
-
    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   Install Visual Studio Binaries
    
+
    
+
    5.1   Install Visual Studio Binaries
    
 
    The installers supplied by BoostPro Computing will download and
 install pre-compiled binaries into the lib\ subdirectory of the
-boost root, typically C:\Program Files\boost\boost_1_39_0\lib\.  If you installed
-all variants of the Boost.Regex binary, you're done with this
+boost root, typically C:\Program Files\boost\boost_1_40_0\lib\.  If you installed
+all variants of the Boost.Regex binary, you're done with this
 step.  Otherwise, please run the installer again and install them
 now.
    
-
    skip to the next step
    
+
    skip to the next step
    
 
    
-
    
-
    5.2   Or, Simplified Build From Source
    
+
    
+
    5.2   Or, Simplified Build From Source
    
 
    If you wish to build from source with Visual C++, you can use a
 simple build procedure described in this section. Open the command prompt
 and change your current directory to the Boost root directory. Then, type
@@ -364,42 +365,42 @@ bootstrap
 
 
    The first command prepares the Boost.Build system for use. The second
 command invokes Boost.Build to build the separately-compiled Boost
-libraries. Please consult the Boost.Build documentation for a list
+libraries. Please consult the Boost.Build documentation for a list
 of options that can be passed to bjam.
    
 
    
-
    
-
    5.3   Or, Build Binaries From Source
    
+
    
+
    5.3   Or, Build Binaries From Source
    
 
    If you're using an earlier version of Visual C++, or a compiler
-from another vendor, you'll need to use Boost.Build to create your
+from another vendor, you'll need to use Boost.Build to create your
 own binaries.
    
 
 
 
-
    Boost.Build is a text-based system for developing, testing, and
+
    Boost.Build is a text-based system for developing, testing, and
 installing software.  To use it, you'll need an executable called
 bjam.
    
 
-
    
-
    5.3.1   Get bjam
    
-
    bjam is the command-line tool that drives the Boost Build
+
    
+
    5.3.1   Get 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.
    
-
    We suggest you download a pre-built bjam executable for your platform.
-Alternatively, you can build bjam yourself using these
+
    We suggest you download a pre-built bjam executable for your platform.
+Alternatively, you can build bjam yourself using these
 instructions.
    
 
    Move the bjam executable into a directory in your PATH.  You can
 see the list of directories in your PATH, separated by semicolons,
 by typing “PATH” at the command prompt.
    
 
    
-
    
-
    5.3.2   Identify Your Toolset
    
+
    
+
    5.3.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
+following table (an up-to-date list is always available in the
 Boost.Build documentation).
    
 
    
 
    Note
    
 
    If you previously chose a toolset for the purposes of
-building bjam, you should assume it won't work and instead
+building bjam, you should assume it won't work and instead
 choose newly from the table below.
    
 
    
 
    
 
 
    [6]This feature of STLPort is deprecated because it's
+
    [6]This feature of STLPort is deprecated because it's
 impossible to make it work transparently to the user; we don't
 recommend it.
    
     
 
 
 
 
 
 
 
    
@@ -428,7 +429,7 @@ known to work well with Boost
 
@@ -491,43 +492,43 @@ a hyphen, e.g. intel-9.0borland-5.4.3. On Windows, append a version
 number even if you only have one version installed (unless you
 are using the msvc or gcc toolsets, which have special version
-detection code) or auto-linking will fail.
    
+detection code) or auto-linking will fail.
    
 
-
    
-
    5.3.3   Select a Build Directory
    
-
    Boost.Build will place all intermediate files it generates while
+
    
+
    5.3.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
 default Boost.Build will create a bin.v2/ subdirectory for that
 purpose in your current working directory.
    
 
    
-
    
-
    5.3.4   Invoke bjam
    
+
    
+
    5.3.4   Invoke bjam
    
 
    Change your current directory to the Boost root directory and
 invoke bjam as follows:
    
 
    -bjam --build-dir=build-directory toolset=toolset-name --build-type=complete stage
+bjam --build-dir=build-directory toolset=toolset-name --build-type=complete stage
 
    
 
    For a complete description of these and other invocation options,
-please see the Boost.Build documentation.
    
-
    For example, your session might look like this:4
    
+please see the Boost.Build documentation.
    
+
    For example, your session might look like this:4
    
 
    -C:\WINDOWS> cd C:\Program Files\boost\boost_1_39_0
-C:\Program Files\boost\boost_1_39_0> bjam ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_40_0
+C:\Program Files\boost\boost_1_40_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --build-type=complete msvc stage
 
    
-
    Be sure to read this note about the appearance of ^,
+
    Be sure to read this note about the appearance of ^,
 More? and quotation marks (") in that line.
    
 
    The option “--build-type=complete” causes bjam to build
 all supported variants of the libraries.  For instructions on how to
-build only specific variants, please ask on the Boost.Build mailing
+build only specific variants, please ask on the Boost.Build mailing
 list.
    
 
 
 
 
    Building the special stage target places Boost
-library binaries in the stage\lib\ subdirectory of your build
+library binaries in the stage\lib\ subdirectory of your build
 directory.
    
 
    
 
    Note
    
@@ -552,12 +553,12 @@ be interested in:
    
 
    Boost.Build can produce a great deal of output, which can
 make it easy to miss problems.  If you want to make sure
 everything is went well, you might redirect the output into a
-file by appending “``>build.log 2>&1``” to your command line.
    
+file by appending “>build.log 2>&1” to your command line.
    
 
    
 
    
 
    
-
    
-
    5.4   Expected Build Output
    
+
    
+
    5.4   Expected Build Output
    
 
    During the process of building Boost libraries, you can expect to
 see some messages printed on the console.  These may include
    
 
      
@@ -580,28 +581,28 @@ look something like:
      
 
 
    
 
    
-
    
-
    5.5   In Case of Build Errors
    
+
    
+
    5.5   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
+formats as described here.  Install the relevant development
 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
-here.  If that isn't your problem or the user-config.jam file
+here.  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.
    
+for your compiler to the Boost.Build mailing list.
    
 
 
 
 
    
 
    
-
    
-
    6   Link Your Program to a Boost Library
    
+
-
    
-
    6.1   Link From Within the Visual Studio IDE
    
-
    Starting with the header-only example project we created
+
    
-
    
-
    6.2   Or, Link From the Command Prompt
    
+
-
    
-
    6.3   Library Naming
    
+
    
+
    6.3   Library Naming
    
 
    
 
    Note
    
 
    If, like Visual C++, your compiler supports auto-linking,
-you can probably skip to the next step.
    
+you can probably skip to the next step.
    
 
    
 
    
 
    
@@ -690,11 +691,11 @@ 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.6
    
+not.6
 
    boost_regex
    
 
    Library name: all boost library filenames begin with boost_.
    
 
    -vc71
    
-
    Toolset tag: identifies the toolset and version used to build
+
    Toolset tag: identifies the toolset and version used to build
 the binary.
    
 
    -mt
    
 
    Threading tag: indicates that the library was
@@ -725,17 +726,17 @@ libraries.
 
    
-
+
-
+
-
+
    como
 Comeau Computing
 Using this toolset may
-require configuring another
+require configuring another
 toolset to act as its backend
 
    
 
    cwusing debug versions of the standard and runtime support libraries.
 
    
 
    yusing a special debug build of Python.using a special debug build of Python.
 
    
 
    dbuilding a debug version of your code.7building a debug version of your code.7
 
    
 
    p
 using the STLPort standard library rather than the default one supplied with
 your compiler.
 
    
 
    nusing STLPort's deprecated “native iostreams” feature.8using STLPort's deprecated “native iostreams” feature.8
 
    
     
 
    
@@ -766,8 +767,8 @@ version number, will also be created.
 
 
 
    
-
    
-
    6.4   Test Your Program
    
+
    
+
    6.4   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:
    
 
    @@ -777,7 +778,7 @@ Subject: Will Success Spoil Rock Hunter?
 ---
 See subject.
 
    
-
    Now, in a command prompt window, type:
    
+
    Now, in a command prompt window, type:
    
 
     path\to\compiled\example < path\to\jayne.txt
 
    
@@ -788,23 +789,23 @@ 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
 we may have a “Book 2 in the Getting Started series” that addresses
 them.  Until then, we suggest you pursue the following resources.
 If you can't find what you need, or there's anything we can do to
-make this document clearer, please post it to the Boost Users'
+make this document clearer, please post it to the Boost Users'
 mailing list.
    
 
 
    
 
    Onward
    
@@ -817,8 +818,8 @@ mailing list.
    
 
-
@@ -827,7 +828,7 @@ built-in decompression as it can be painfully slow for large archives.
    
 
 
    [1]We recommend
-downloading boost_1_39_0.7z and using 7-Zip to decompress
+
    [1]We recommend
+downloading boost_1_40_0.7z and using 7-Zip to decompress
 it.  We no longer recommend .zip files for Boost because they are twice
 as large as the equivalent .7z files.  We don't recommend using Windows'
 built-in decompression as it can be painfully slow for large archives.
    
 
    
-
    
 
 
    [2]If you used the installer from Boost
+
    [2]If you used the installer from Boost
 Consulting and deselected “Source and Documentation”  (it's
 selected by default), you won't see the libs/ subdirectory.
 That won't affect your ability to use precompiled binaries, but
@@ -837,7 +838,7 @@ you won't be able to rebuild libraries from scratch.
    
 
    
-
@@ -846,7 +847,7 @@ used in the examples.
    
 
 
    [3]There's no problem using Boost with precompiled headers;
+
    [3]There's no problem using Boost with precompiled headers;
 these instructions merely avoid precompiled headers because it
 would require Visual Studio-specific changes to the source code
 used in the examples.
    
 
    
-
    
 
 
    [4]
    In this example, the caret character ^ is a
+
    [4]
    In this example, the caret character ^ is a
 way of continuing the command on multiple lines, and must be the
 final character used on the line to be continued (i.e. do
 not follow it with spaces).  The command prompt responds with
@@ -873,7 +874,7 @@ command-line argument contains spaces, as in
    
 
-
    
 
 
    [5]Remember that warnings are specific to each compiler
+
    [5]Remember that warnings are specific to each compiler
 implementation.  The developer of a given Boost library might
 not have access to your compiler.  Also, some warnings are
 extremely difficult to eliminate in generic code, to the point
@@ -884,7 +885,7 @@ have any source code mechanism for suppressing warnings.
    
 
    
-
@@ -893,7 +894,7 @@ same name.
    
 
 
    [6]This convention distinguishes the static version of
+
    [6]This convention distinguishes the static version of
 a Boost library from the import library for an
 identically-configured Boost DLL, which would otherwise have the
 same name.
    
 
    
-
    
 
 
    [7]These libraries were compiled without optimization
+
    [7]These libraries were compiled without optimization
 or inlining, with full debug symbols enabled, and without
 NDEBUG #defined.  Although it's true that sometimes
 these choices don't affect binary compatibility with other
@@ -903,7 +904,7 @@ compiled code, you can't count on that with Boost libraries.
    
 
    
-
    
 
 
    [8]This feature of STLPort is deprecated because it's
+
    [8]This feature of STLPort is deprecated because it's
 impossible to make it work transparently to the user; we don't
 recommend it.