From 6a80bedfc9da3eb5004de5af49e6b1834a62f0ed Mon Sep 17 00:00:00 2001 From: Daniel James Date: Wed, 22 Oct 2008 19:16:22 +0000 Subject: [PATCH 01/10] Update the version number in the getting started guide. [SVN r49435] --- getting_started/detail/release-variables.rst | 6 +- getting_started/index.html | 27 +- getting_started/unix-variants.html | 252 +++++++------- getting_started/windows.html | 327 +++++++++---------- 4 files changed, 305 insertions(+), 307 deletions(-) diff --git a/getting_started/detail/release-variables.rst b/getting_started/detail/release-variables.rst index 7c32fb2..b3d051c 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.36.0 -.. |boost_ver| replace:: ``boost_1_36_0`` -.. |boost_ver-bold| replace:: **boost_1_36_0** +.. |boost-version-number| replace:: 1.37.0 +.. |boost_ver| replace:: ``boost_1_37_0`` +.. |boost_ver-bold| replace:: **boost_1_37_0** .. _sf-download: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041 diff --git a/getting_started/index.html b/getting_started/index.html index 07428bd..cfebb13 100644 --- a/getting_started/index.html +++ b/getting_started/index.html @@ -3,32 +3,31 @@ - + Boost Getting Started
-

Getting Started

- +

Getting Started

Use the latest version of this Getting Started guide

-

The Boost website version of this Getting Started guide may +

The Boost website version of this Getting Started guide may have undated information, such as the location of additional installers or improved installation procedures, so you might want use that version if you've got an Internet connection available.

-
-

Welcome

+
+

Welcome

Welcome to the Boost libraries! By the time you've completed this tutorial, you'll be at least somewhat comfortable with the contents of a Boost distribution and how to go about using it.

-
-

What's Here

+
+

What's Here

This document is designed to be an extremely gentle introduction, so we included a fair amount of material that may already be very familiar to you. To keep things simple, we also left out some @@ -36,8 +35,8 @@ information intermediate and advanced users will probably want. At the end of this document, we'll refer you on to resources that can help you pursue these topics further.

-
-

Preliminaries

+
+

Preliminaries

We use one typographic convention that might not be immediately obvious: italic text in examples is meant as a descriptive placeholder for something else, usually information that you'll @@ -48,16 +47,16 @@ provide. For example:

Here you're expected to imagine replacing the text “your name” with your actual name.

-
-

Ready?

+
+

Ready?

Let's go!

-
Next: Getting Started on Microsoft Windows
-
or: Getting Started on Unix variants (e.g. Linux, MacOS)
+
Next: Getting Started on Microsoft Windows
+
or: Getting Started on Unix variants (e.g. Linux, MacOS)
diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html index 050b01a..c3ac2a8 100644 --- a/getting_started/unix-variants.html +++ b/getting_started/unix-variants.html @@ -3,15 +3,14 @@ - + Boost Getting Started on Unix Variants
-

Getting Started on Unix Variants

- +

Getting Started on Unix Variants

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

Index

+
+

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_36_0.tar.bz2.

    +

  2. Download boost_1_37_0.tar.bz2.

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

    -tar --bzip2 -xf /path/to/boost_1_36_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_37_0.tar.bz2
@@ -79,19 +78,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_36_0/ .................The “boost root directory”
+boost_1_37_0/ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost/ .........................All Boost Header files
     
@@ -123,7 +122,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.
 
    
@@ -136,7 +135,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_36_0) is +

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

      3. @@ -165,8 +164,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.

    @@ -179,25 +178,25 @@ 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 +204,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 +229,7 @@ int main()

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

    -c++ -I path/to/boost_1_36_0 example.cpp -o example
+c++ -I path/to/boost_1_37_0 example.cpp -o example

    To test the result, type:

    @@ -239,29 +238,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_36_0
+$ cd path/to/boost_1_37_0
 $ ./configure --help
 
    
 
    Select your configuration options and invoke ./configure again
@@ -282,38 +281,38 @@ 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.
    
-
    Boost provides pre-compiled bjam executables for a variety of platforms.
-Alternatively, you can build bjam yourself using these
+
    Boost provides pre-compiled bjam executables for a variety of platforms.
+Alternatively, you can build bjam yourself using these
 instructions.
    
 
    
-
    
-
    5.2.2   Identify Your Toolset
    
+
    
+
    5.2.2   Identify Your Toolset
    
 
    First, find the toolset corresponding to your compiler in the
 following table.
    
 
    
 
    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.
    
 
    
 
@@ -342,7 +341,7 @@ known to work well with Boost
@@ -408,36 +407,36 @@ 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 [--build-type=complete] stage
+bjam --build-dir=build-directory --toolset=toolset-name [--build-type=complete] stage
 
    
 
    For example, your session might look like this:
    
 
    -$ cd ~/boost_1_36_0
+$ cd ~/boost_1_37_0
 $ bjam --build-dir=/tmp/build-boost --toolset=gcc stage
 
    
 
    That will build static and shared non-debug multi-threaded variations of the libraries. To build all variations:
    
 
    -$ cd ~/boost_1_36_0
+$ cd ~/boost_1_37_0
 $ bjam --build-dir=/tmp/build-boost --toolset=gcc --build-type=complete stage
 
    
 
 
 
 
    Building the special stage target places Boost
-library binaries in the stage/ subdirectory of your build
+library binaries in the stage/ subdirectory of your build
 directory.
    
 
    
 
    Note
    
@@ -459,8 +458,8 @@ be interested in:
    
 
 
    
 
    
-
    
-
    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
    
 
      
@@ -483,29 +482,29 @@ 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
-in the Boost.Build documentation.  If that isn't your problem or
+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.
    
+Boost.Build mailing list.
    
 
 
 
 
    
 
    
-
    
-
+
-
+
-
+
    
 
    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
 
    
     
 
    
@@ -641,7 +640,7 @@ convention.  On most unix-style platforms the extensions are
 .a and .so for static libraries (archives) and shared
 libraries, respectively.  On Windows, .dll indicates a shared
 library and (except for static libraries built by the gcc
-toolset, whose names always end in .a) .lib indicates a
+toolset, whose names always end in .a) .lib indicates a
 static or import library.  Where supported by toolsets on unix
 variants, a full version extension is added (e.g. ".so.1.34") and
 a symbolic link to the library file, named without the trailing
@@ -652,8 +651,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:
    
 
    @@ -692,23 +691,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
    
@@ -721,16 +720,17 @@ 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.
    
     
 
    
@@ -740,7 +740,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
@@ -751,7 +751,7 @@ have any source code mechanism for suppressing warnings.
    
 
    
-
@@ -760,7 +760,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
@@ -770,7 +770,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 fe3fcf5..3821856 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -3,84 +3,83 @@
 
-
+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
+The 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 Computing.  We especially recommend using
+or see 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 Boost.Regex binaries when given the option.
    
+install 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_36_0.7z or boost_1_36_0.zip and unpack it to install a complete Boost
-distribution.1
    
+download boost_1_37_0.7z or boost_1_37_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_36_0\ .................The “boost root directory”
+boost_1_37_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -112,7 +111,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.
 
    
@@ -125,7 +124,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_36_0) is
+
    2. The path to the boost root directory (often C:\Program Files\boost\boost_1_37_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
      
 
      3. 
@@ -159,8 +158,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.
    
 
    
@@ -173,25 +172,25 @@ 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.
      • 
 
    
@@ -199,8 +198,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
@@ -221,11 +220,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
@@ -249,14 +248,14 @@ cd path\to\some\directory
 
 
    followed by Return.  For example,
    
 
    -cd C:\Program Files\boost\boost_1_36_0
+cd C:\Program Files\boost\boost_1_37_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…
      
 
      • 
@@ -274,12 +273,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_36_0
      
+
      C:\Program Files\boost\boost_1_37_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.
      
@@ -294,10 +293,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
    
 
    
@@ -307,12 +306,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_36_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_37_0 path\to\example.cpp
 
    
 
    To test the result, type:
    
 
    @@ -322,62 +321,62 @@ 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 will download and
 install pre-compiled binaries into the lib\ subdirectory of the
-boost root, typically C:\Program Files\boost\boost_1_36_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_37_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, Build Binaries From Source
    
+
    
+
    5.2   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.2.1   Get bjam
    
-
    bjam is the command-line tool that drives the Boost Build
+
    
+
    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.
    
-
    Boost provides pre-compiled bjam executables for a variety of platforms.
-Alternatively, you can build bjam yourself using these
+
    Boost provides pre-compiled bjam executables for a variety of platforms.
+Alternatively, you can build bjam yourself using these
 instructions.
    
 
    
-
    
-
    5.2.2   Identify Your Toolset
    
+
    
+
    5.2.2   Identify Your Toolset
    
 
    First, find the toolset corresponding to your compiler in the
 following table.
    
 
    
 
    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.
    
     
 
 
 
 
 
 
 
    
@@ -406,7 +405,7 @@ known to work well with Boost
 
@@ -473,37 +472,37 @@ 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.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 [--build-type=complete] stage
+bjam --build-dir=build-directory --toolset=toolset-name [--build-type=complete] stage
 
    
-
    For example, your session might look like this:4
    
+
    For example, your session might look like this:4
    
 
    -C:\WINDOWS> cd C:\Program Files\boost\boost_1_36_0
-C:\Program Files\boost\boost_1_36_0> bjam ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_37_0
+C:\Program Files\boost\boost_1_37_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --toolset=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 above example session will build static and shared non-debug multi-threaded
 variations of the libraries. To build all variations:
    
 
    -C:\WINDOWS> cd C:\Program Files\boost\boost_1_36_0
-C:\Program Files\boost\boost_1_36_0> bjam ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_37_0
+C:\Program Files\boost\boost_1_37_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --toolset=msvc --build-type=complete stage
 
    
@@ -511,7 +510,7 @@ More? --toolset=msvc --build-type=complete sta
 
 
 
    Building the special stage target places Boost
-library binaries in the stage\ subdirectory of your build
+library binaries in the stage\ subdirectory of your build
 directory.
    
 
    
 
    Note
    
@@ -533,8 +532,8 @@ be interested in:
    
 
 
    
 
    
-
    
-
    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
    
 
      
@@ -557,29 +556,29 @@ 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
-in the Boost.Build documentation.  If that isn't your problem or
+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.
    
+Boost.Build mailing list.
    
 
 
 
 
    
 
    
-
    
-
+
-
+
-
+
    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
 
    
     
 
    
@@ -734,7 +733,7 @@ convention.  On most unix-style platforms the extensions are
 .a and .so for static libraries (archives) and shared
 libraries, respectively.  On Windows, .dll indicates a shared
 library and (except for static libraries built by the gcc
-toolset, whose names always end in .a) .lib indicates a
+toolset, whose names always end in .a) .lib indicates a
 static or import library.  Where supported by toolsets on unix
 variants, a full version extension is added (e.g. ".so.1.34") and
 a symbolic link to the library file, named without the trailing
@@ -745,8 +744,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:
    
 
    @@ -756,7 +755,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
 
    
@@ -767,23 +766,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
    
@@ -796,8 +795,8 @@ mailing list.
    
 
-
@@ -806,7 +805,7 @@ built-in decompression as it can be painfully slow for large archives.
    
 
 
    [1]We recommend
-downloading boost_1_36_0.7z and using 7-Zip to decompress
+
    [1]We recommend
+downloading boost_1_37_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
@@ -816,7 +815,7 @@ you won't be able to rebuild libraries from scratch.
    
 
    
-
@@ -825,7 +824,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
@@ -852,7 +851,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
@@ -863,7 +862,7 @@ have any source code mechanism for suppressing warnings.
    
 
    
-
@@ -872,7 +871,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
@@ -882,7 +881,7 @@ compiled code, you can't count on that with Boost libraries.
    
 
    
-

From 63176af257bd63cb7feae984888882977761633c Mon Sep 17 00:00:00 2001
From: Beman Dawes 
Date: Wed, 22 Oct 2008 20:26:04 +0000
Subject: [PATCH 02/10] Getting started: update to 1.37.0. The trac Release
 Manager's Checklist was also updated so that Getting Started will get updated
 right at the start of the release cycle.

[SVN r49438]
---
 getting_started/index.html         |  27 +--
 getting_started/index.rst          |   2 +-
 getting_started/unix-variants.html | 234 +++++++++++-----------
 getting_started/windows.html       | 299 +++++++++++++++--------------
 4 files changed, 282 insertions(+), 280 deletions(-)

diff --git a/getting_started/index.html b/getting_started/index.html
index cfebb13..c8b8021 100644
--- a/getting_started/index.html
+++ b/getting_started/index.html
@@ -3,31 +3,32 @@
 
 
 
-
+
 Boost Getting Started
 
 
 
 
    
-
     Getting Started
    
+
     Getting Started
    
+
 
 
 
 
    
 
    Use the latest version of this Getting Started guide
    
-
    The Boost website version of this Getting Started guide may
+
    The Boost website version of this Getting Started guide may
 have undated information, such as the location of additional installers
 or improved installation procedures, so you might want use that version
 if you've got an Internet connection available.
    
 
    
-
    
-
    Welcome
    
+
    
+
    Welcome
    
 
    Welcome to the Boost libraries!  By the time you've completed this
 tutorial, you'll be at least somewhat comfortable with the contents
 of a Boost distribution and how to go about using it.
    
 
    
-
    
-
    What's Here
    
+
    
+
    What's Here
    
 
    This document is designed to be an extremely gentle introduction,
 so we included a fair amount of material that may already be very
 familiar to you.  To keep things simple, we also left out some
@@ -35,8 +36,8 @@ information intermediate and advanced users will probably want.  At
 the end of this document, we'll refer you on to resources that can
 help you pursue these topics further.
    
 
    
-
    
-
    Preliminaries
    
+
    
+
    Preliminaries
    
 
    We use one typographic convention that might not be immediately
 obvious: italic text in examples is meant as a descriptive
 placeholder for something else, usually information that you'll
@@ -47,16 +48,16 @@ provide.  For example:
    
 
    Here you're expected to imagine replacing the text “your name” with
 your actual name.
    
 
    
-
    
-
    Ready?
    
+
    
+
    Ready?
    
 
    Let's go!
    
 
    
 
    
 
    
 
    
 
    
-
    Next: Getting Started on Microsoft Windows
    
-
    or: Getting Started on Unix variants (e.g. Linux, MacOS)
    
+
    Next: Getting Started on Microsoft Windows
    
+
    or: Getting Started on Unix variants (e.g. Linux, MacOS)
    
 
    
 
 
    
diff --git a/getting_started/index.rst b/getting_started/index.rst
index d12b400..025226e 100644
--- a/getting_started/index.rst
+++ b/getting_started/index.rst
@@ -20,7 +20,7 @@ __ ../../index.htm
   if you've got an Internet connection available.
 
   .. _`Boost website version of this Getting Started guide`:
-       http://www.boost.org/doc/libs/1_36_0/more/getting_started/index.html
+       http://www.boost.org/doc/libs/release/more/getting_started/index.html
 
 Welcome
 -------
diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html
index c3ac2a8..f536074 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,43 +27,43 @@
   .. _`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_37_0.tar.bz2.
      
+
    2. Download boost_1_37_0.tar.bz2.
      
 
      3. 
 
    3. In the directory where you want to put the Boost installation,
 execute
      
@@ -78,16 +79,16 @@ 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_37_0/ .................The “boost root directory”
@@ -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.
 
    
@@ -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,25 +179,25 @@ 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.
      • 
 
    
@@ -204,8 +205,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
@@ -238,25 +239,25 @@ 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):
    
 
    @@ -281,38 +282,38 @@ 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.
    
-
    Boost provides pre-compiled bjam executables for a variety of platforms.
-Alternatively, you can build bjam yourself using these
+
    Boost provides pre-compiled bjam executables for a variety of platforms.
+Alternatively, you can build bjam yourself using these
 instructions.
    
 
    
-
    
-
    5.2.2   Identify Your Toolset
    
+
    
+
    5.2.2   Identify Your Toolset
    
 
    First, find the toolset corresponding to your compiler in the
 following table.
    
 
    
 
    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.
    
 
    
 
    
 
 
    [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.
    
 
    
@@ -341,7 +342,7 @@ known to work well with Boost
 
@@ -407,20 +408,20 @@ 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 [--build-type=complete] stage
+bjam --build-dir=build-directory --toolset=toolset-name [--build-type=complete] stage
 
    
 
    For example, your session might look like this:
    
 
    @@ -436,7 +437,7 @@ $ bjam --build-dir=/tmp/build-boost --toolset=
 
 
 
    Building the special stage target places Boost
-library binaries in the stage/ subdirectory of your build
+library binaries in the stage/ subdirectory of your build
 directory.
    
 
    
 
    Note
    
@@ -458,8 +459,8 @@ be interested in:
    
 
 
    
 
    
-
    
-
    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
    
 
      
@@ -482,29 +483,29 @@ 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
-in the Boost.Build documentation.  If that isn't your problem or
+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.
    
+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
 
    
 
    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.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
 
    
     
 
    
@@ -640,7 +641,7 @@ convention.  On most unix-style platforms the extensions are
 .a and .so for static libraries (archives) and shared
 libraries, respectively.  On Windows, .dll indicates a shared
 library and (except for static libraries built by the gcc
-toolset, whose names always end in .a) .lib indicates a
+toolset, whose names always end in .a) .lib indicates a
 static or import library.  Where supported by toolsets on unix
 variants, a full version extension is added (e.g. ".so.1.34") and
 a symbolic link to the library file, named without the trailing
@@ -651,8 +652,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:
    
 
    @@ -691,23 +692,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
    
@@ -720,17 +721,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.
    
     
 
    
@@ -740,7 +740,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
@@ -751,7 +751,7 @@ have any source code mechanism for suppressing warnings.
    
 
    
-
@@ -760,7 +760,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
@@ -770,7 +770,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 3821856..6274efb 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -3,80 +3,81 @@
 
-
+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
+The 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 Computing.  We especially recommend using
+or see 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 Boost.Regex binaries when given the option.
    
+install 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_37_0.7z or boost_1_37_0.zip and unpack it to install a complete Boost
-distribution.1
    
+download boost_1_37_0.7z or boost_1_37_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_37_0\ .................The “boost root directory”
@@ -111,7 +112,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.
 
    
@@ -158,8 +159,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.
    
 
    
@@ -172,25 +173,25 @@ 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.
      • 
 
    
@@ -198,8 +199,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
@@ -220,11 +221,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
@@ -254,8 +255,8 @@ cd C:\Program ^) 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…
      
 
      • 
@@ -278,7 +279,7 @@ Directories, enter the path to the Boost root directory, for example
      
 
 
    • 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.
      
@@ -293,10 +294,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
    
 
    
@@ -306,8 +307,8 @@ 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:
    
 
    @@ -321,62 +322,62 @@ 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 will download and
 install pre-compiled binaries into the lib\ subdirectory of the
 boost root, typically C:\Program Files\boost\boost_1_37_0\lib\.  If you installed
-all variants of the Boost.Regex binary, you're done with this
+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, Build Binaries From Source
    
+
    
+
    5.2   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.2.1   Get bjam
    
-
    bjam is the command-line tool that drives the Boost Build
+
    
+
    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.
    
-
    Boost provides pre-compiled bjam executables for a variety of platforms.
-Alternatively, you can build bjam yourself using these
+
    Boost provides pre-compiled bjam executables for a variety of platforms.
+Alternatively, you can build bjam yourself using these
 instructions.
    
 
    
-
    
-
    5.2.2   Identify Your Toolset
    
+
    
+
    5.2.2   Identify Your Toolset
    
 
    First, find the toolset corresponding to your compiler in the
 following table.
    
 
    
 
    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.
    
     
 
 
 
 
 
 
 
    
@@ -405,7 +406,7 @@ known to work well with Boost
 
@@ -472,31 +473,31 @@ 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.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 [--build-type=complete] stage
+bjam --build-dir=build-directory --toolset=toolset-name [--build-type=complete] stage
 
    
-
    For example, your session might look like this:4
    
+
    For example, your session might look like this:4
    
 
     C:\WINDOWS> cd C:\Program Files\boost\boost_1_37_0
 C:\Program Files\boost\boost_1_37_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --toolset=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 above example session will build static and shared non-debug multi-threaded
 variations of the libraries. To build all variations:
    
@@ -510,7 +511,7 @@ More? --toolset=msvc --build-type=complete sta
 
 
 
    Building the special stage target places Boost
-library binaries in the stage\ subdirectory of your build
+library binaries in the stage\ subdirectory of your build
 directory.
    
 
    
 
    Note
    
@@ -532,8 +533,8 @@ be interested in:
    
 
 
    
 
    
-
    
-
    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
    
 
      
@@ -556,29 +557,29 @@ 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
-in the Boost.Build documentation.  If that isn't your problem or
+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.
    
+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.
    
 
    
 
    
 
    
@@ -667,11 +668,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
@@ -702,17 +703,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
 
    
     
 
    
@@ -733,7 +734,7 @@ convention.  On most unix-style platforms the extensions are
 .a and .so for static libraries (archives) and shared
 libraries, respectively.  On Windows, .dll indicates a shared
 library and (except for static libraries built by the gcc
-toolset, whose names always end in .a) .lib indicates a
+toolset, whose names always end in .a) .lib indicates a
 static or import library.  Where supported by toolsets on unix
 variants, a full version extension is added (e.g. ".so.1.34") and
 a symbolic link to the library file, named without the trailing
@@ -744,8 +745,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:
    
 
    @@ -755,7 +756,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
 
    
@@ -766,23 +767,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
    
@@ -795,8 +796,8 @@ mailing list.
    
 
-
@@ -805,7 +806,7 @@ built-in decompression as it can be painfully slow for large archives.
    
 
 
    [1]We recommend
-downloading boost_1_37_0.7z and using 7-Zip to decompress
+
    [1]We recommend
+downloading boost_1_37_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
@@ -815,7 +816,7 @@ you won't be able to rebuild libraries from scratch.
    
 
    
-
@@ -824,7 +825,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
@@ -851,7 +852,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
@@ -862,7 +863,7 @@ have any source code mechanism for suppressing warnings.
    
 
    
-
@@ -871,7 +872,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
@@ -881,7 +882,7 @@ compiled code, you can't count on that with Boost libraries.
    
 
    
-

From 62c3563838527198d11ad2991f4b75643aa7c0b9 Mon Sep 17 00:00:00 2001
From: Dave Abrahams 
Date: Sat, 1 Nov 2008 19:17:28 +0000
Subject: [PATCH 03/10] Updates for 1.37 based on commentary by Paul Bristow
 and experiences with students at MathWorks.

Also cleaned up the use of --build-type=complete, which was
mis-formatted, and is usually inappropriate on *nix anyway.


[SVN r49524]
---
 .../detail/build-from-source-head.rst         |  9 +++--
 getting_started/detail/common-unix.rst        |  3 ++
 getting_started/detail/common-windows.rst     |  4 +++
 getting_started/index.html                    |  2 +-
 getting_started/unix-variants.html            | 15 ++++----
 getting_started/unix-variants.rst             |  9 ++---
 getting_started/windows.html                  | 23 ++++++------
 getting_started/windows.rst                   | 36 +++++++++----------
 8 files changed, 52 insertions(+), 49 deletions(-)

diff --git a/getting_started/detail/build-from-source-head.rst b/getting_started/detail/build-from-source-head.rst
index 276f6f5..f031648 100644
--- a/getting_started/detail/build-from-source-head.rst
+++ b/getting_started/detail/build-from-source-head.rst
@@ -6,7 +6,7 @@ Boost.Build_ is a text-based system for developing, testing, and
 installing software.  To use it, you'll need an executable called
 ``bjam``.
 
-.. |precompiled-bjam| replace:: pre-compiled ``bjam`` executables
+.. |precompiled-bjam| replace:: download a pre-built ``bjam`` executable
 
 
 .. _precompiled-bjam: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941
@@ -22,12 +22,15 @@ Get ``bjam``
 system.  To build Boost binaries, you'll invoke ``bjam`` from the
 Boost root.  
 
-Boost provides |precompiled-bjam|_ for a variety of platforms.
+We suggest you |precompiled-bjam|_ for your platform.
 Alternatively, you can build ``bjam`` yourself using `these
 instructions`__.
 
 __ `building bjam`_
 
+Move the ``bjam`` executable into a directory in your PATH.  You can
+see the list of directories in your PATH, separated by |pathsep|\ s,
+by typing “\ |path|\ ” at the command prompt.
 
 .. _toolset:
 .. _toolset-name:
@@ -123,4 +126,4 @@ invoke ``bjam`` as follows:
 
 .. parsed-literal::
 
-  bjam **--build-dir=**\ |build-directory|_ **--toolset=**\ |toolset-name|_ *[*\ **--build-type=complete**\ *]* stage
+  bjam **--build-dir=**\ |build-directory|_ **--toolset=**\ |toolset-name|_ |build-type-complete| stage
diff --git a/getting_started/detail/common-unix.rst b/getting_started/detail/common-unix.rst
index c1cdf49..09ad5d8 100644
--- a/getting_started/detail/common-unix.rst
+++ b/getting_started/detail/common-unix.rst
@@ -20,5 +20,8 @@
 
 .. |command-line tool| replace:: command-line tool
 
+.. |pathsep| replace:: colon
+
+.. |path| replace:: ``echo $PATH``
 
 .. include:: common.rst
diff --git a/getting_started/detail/common-windows.rst b/getting_started/detail/common-windows.rst
index fa0102c..75ba004 100644
--- a/getting_started/detail/common-windows.rst
+++ b/getting_started/detail/common-windows.rst
@@ -31,4 +31,8 @@
 
 .. |command-line tool| replace:: `command-line tool`_
 
+.. |pathsep| replace:: semicolon
+
+.. |path| replace:: ``PATH``
+
 .. include:: common.rst
diff --git a/getting_started/index.html b/getting_started/index.html
index c8b8021..86a98dd 100644
--- a/getting_started/index.html
+++ b/getting_started/index.html
@@ -3,7 +3,7 @@
 
 
 
-
+
 Boost Getting Started
 
 
diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html
index f536074..32a10ec 100644
--- a/getting_started/unix-variants.html
+++ b/getting_started/unix-variants.html
@@ -3,7 +3,7 @@
 
 
 
-
+
 Boost Getting Started on Unix Variants
 
 
@@ -302,9 +302,12 @@ installing software.  To use it, you'll need an executable called
 
    bjam is the command-line tool that drives the Boost Build
 system.  To build Boost binaries, you'll invoke bjam from the
 Boost root.
    
-
    Boost provides pre-compiled bjam executables for a variety of platforms.
+
    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
    
@@ -421,18 +424,14 @@ purpose in your current working directory.
    
 
    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   stage
 
    
 
    For example, your session might look like this:
    
 
     $ cd ~/boost_1_37_0
 $ bjam --build-dir=/tmp/build-boost --toolset=gcc stage
 
    
-
    That will build static and shared non-debug multi-threaded variations of the libraries. To build all variations:
    
-
    -$ cd ~/boost_1_37_0
-$ bjam --build-dir=/tmp/build-boost --toolset=gcc --build-type=complete 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``”.
    
 
 
 
diff --git a/getting_started/unix-variants.rst b/getting_started/unix-variants.rst
index f87eacb..548343e 100644
--- a/getting_started/unix-variants.rst
+++ b/getting_started/unix-variants.rst
@@ -142,12 +142,7 @@ For example, your session might look like this:
    $ cd ~/|boost_ver|
    $ bjam **--build-dir=**\ /tmp/build-boost **--toolset=**\ gcc stage
 
-That will build static and shared non-debug multi-threaded variations of the libraries. To build all variations:
-
-.. parsed-literal::
-
-   $ cd ~/|boost_ver|
-   $ bjam **--build-dir=**\ /tmp/build-boost **--toolset=**\ gcc **--build-type=complete** 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``”.
 
 .. include:: detail/build-from-source-tail.rst
 
@@ -237,6 +232,8 @@ Spoil Rock Hunter?”
 .. [#lowercase-l] That option is a dash followed by a lowercase “L”
    character, which looks very much like a numeral 1 in some fonts.
 
+.. |build-type-complete| replace:: `` `` 
+
 .. include:: detail/common-footnotes.rst
 .. include:: detail/release-variables.rst
 .. include:: detail/common-unix.rst
diff --git a/getting_started/windows.html b/getting_started/windows.html
index 6274efb..a4dea4e 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -3,7 +3,7 @@
 
 
 
-
+
 Boost Getting Started on Windows
 
 
@@ -366,9 +366,12 @@ installing software.  To use it, you'll need an executable called
 
    bjam is the command-line tool that drives the Boost Build
 system.  To build Boost binaries, you'll invoke bjam from the
 Boost root.
    
-
    Boost provides pre-compiled bjam executables for a variety of platforms.
+
    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.2.2   Identify Your Toolset
    
@@ -488,25 +491,21 @@ purpose in your current working directory.
    
 
    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 example, your session might look like this:4
    
 
     C:\WINDOWS> cd C:\Program Files\boost\boost_1_37_0
 C:\Program Files\boost\boost_1_37_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
-More? --toolset=msvc stage
+More? --toolset= --build-type=complete msvc stage
 
    
 
    Be sure to read this note about the appearance of ^,
 More? and quotation marks (") in that line.
    
-
    The above example session will build static and shared non-debug multi-threaded
-variations of the libraries. To build all variations:
    
-
    -C:\WINDOWS> cd C:\Program Files\boost\boost_1_37_0
-C:\Program Files\boost\boost_1_37_0> bjam ^
-More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
-More? --toolset=msvc --build-type=complete stage
-
    
+
    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
+list.
    
 
 
 
diff --git a/getting_started/windows.rst b/getting_started/windows.rst
index dab2cb2..6026dd7 100644
--- a/getting_started/windows.rst
+++ b/getting_started/windows.rst
@@ -35,14 +35,16 @@ __ ../../index.htm
 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 undated information on installers as they become available,
-or see `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 Boost.Regex_ binaries when given the option.
+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
+undated information on installers as they become available, or see
+`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_
+binaries when given the option.
 
 .. _`Boost website version of this Getting Started guide`:
        http://www.boost.org/doc/libs/1_36_0/more/getting_started/index.html
@@ -186,7 +188,7 @@ To test the result, type:
 Install Visual Studio Binaries
 ------------------------------
 
-The installers will download and
+The installers supplied by BoostPro Computing will download and
 install pre-compiled binaries into the ``lib\`` subdirectory of the
 boost root, typically |default-root|\ ``\lib\``.  If you installed
 all variants of the Boost.Regex_ binary, you're done with this
@@ -213,20 +215,15 @@ For example, your session might look like this: [#continuation]_
    C:\\WINDOWS> cd |default-root|
    |default-root|> bjam **^**
    More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^**
-   More? **--toolset=**\ msvc stage
+   More? **--toolset=**\  **--build-type=complete** msvc stage
 
 Be sure to read `this note`__ about the appearance of ``^``,
 ``More?`` and quotation marks (``"``) in that line.
 
-The above example session will build static and shared non-debug multi-threaded
-variations of the libraries. To build all variations:
-
-.. parsed-literal::
-
-   C:\\WINDOWS> cd |default-root|
-   |default-root|> bjam **^**
-   More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^**
-   More? **--toolset=**\ msvc **--build-type=complete** stage
+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
+list`_.
 
 __ continuation_
 
@@ -355,6 +352,7 @@ Spoil Rock Hunter?”
 
 .. _`boost.zip`: `sf-download`_
 
+.. |build-type-complete| replace:: **--build-type=complete**
 
 .. include:: detail/common-footnotes.rst
 .. include:: detail/release-variables.rst

From df9035becb2caf12e4d6c073806a583a949f0d5a Mon Sep 17 00:00:00 2001
From: Dave Abrahams 
Date: Sat, 1 Nov 2008 19:34:35 +0000
Subject: [PATCH 04/10] Added information about redirecting build output into a
 file.

[SVN r49525]
---
 .../detail/build-from-source-tail.rst         |  5 ++++
 getting_started/unix-variants.html            |  7 +++++
 getting_started/windows.html                  | 27 ++++++++++++-------
 3 files changed, 30 insertions(+), 9 deletions(-)

diff --git a/getting_started/detail/build-from-source-tail.rst b/getting_started/detail/build-from-source-tail.rst
index 5a07b71..c8377ad 100644
--- a/getting_started/detail/build-from-source-tail.rst
+++ b/getting_started/detail/build-from-source-tail.rst
@@ -23,6 +23,11 @@ be interested in:
 * choosing a specific build variant by adding ``release`` or
   ``debug`` to the command line.
 
+.. Note:: 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.
+
 Expected Build Output
 ---------------------
 
diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html
index 32a10ec..9627600 100644
--- a/getting_started/unix-variants.html
+++ b/getting_started/unix-variants.html
@@ -456,6 +456,13 @@ be interested in:
    
 
  • choosing a specific build variant by adding release or
 debug to the command line.
    • 
 
+
    
+
    Note
    
+
    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.
    
+
    
 
    
 
 
    
diff --git a/getting_started/windows.html b/getting_started/windows.html
index a4dea4e..a5cd5f6 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -60,14 +60,16 @@ not supported—they may or may not work.
    
 
    
 
    
 
    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 undated information on installers as they become available,
-or see 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 Boost.Regex binaries when given the option.
    
+
    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
+undated information on installers as they become available, or see
+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
+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_37_0.7z or boost_1_37_0.zip and unpack it to install a complete Boost
@@ -341,7 +343,7 @@ correctly identified the 
 
    5.1   Install Visual Studio Binaries
    
-
    The installers will download and
+
    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_37_0\lib\.  If you installed
 all variants of the Boost.Regex binary, you're done with this
@@ -530,6 +532,13 @@ be interested in:
    
 
  • choosing a specific build variant by adding release or
 debug to the command line.
    • 
 
+
    
+
    Note
    
+
    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.
    
+
    
 
    
 
 
    

From 6c9f186f7920da5642dabd8a4d9239dc79e64329 Mon Sep 17 00:00:00 2001
From: Beman Dawes 
Date: Mon, 3 Nov 2008 15:18:21 +0000
Subject: [PATCH 05/10] Prep for 1.38.0

[SVN r49556]
---
 getting_started/detail/release-variables.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/getting_started/detail/release-variables.rst b/getting_started/detail/release-variables.rst
index b3d051c..384d7a8 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.37.0
-.. |boost_ver| replace:: ``boost_1_37_0``
-.. |boost_ver-bold| replace:: **boost_1_37_0**
+.. |boost-version-number| replace:: 1.38.0
+.. |boost_ver| replace:: ``boost_1_38_0``
+.. |boost_ver-bold| replace:: **boost_1_38_0**
 
 .. _sf-download: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041

From 0e798313a1dfc1aa9d9bdce60746968354f1db40 Mon Sep 17 00:00:00 2001
From: Beman Dawes 
Date: Mon, 3 Nov 2008 15:38:36 +0000
Subject: [PATCH 06/10] Prep for 1.38.0

[SVN r49562]
---
 getting_started/unix-variants.html | 22 +++++++++++-----------
 getting_started/windows.html       | 30 +++++++++++++++---------------
 2 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html
index 9627600..f3bd8b1 100644
--- a/getting_started/unix-variants.html
+++ b/getting_started/unix-variants.html
@@ -63,12 +63,12 @@
 
    The most reliable way to get a copy of Boost is to download a
 distribution from SourceForge:
    
 
      
-
    1. Download boost_1_37_0.tar.bz2.
      
+
    2. Download boost_1_38_0.tar.bz2.
      
 
      3. 
 
    3. In the directory where you want to put the Boost installation,
 execute
      
 
      -tar --bzip2 -xf /path/to/boost_1_37_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_38_0.tar.bz2
 
      
 
      4. 
 
    
@@ -91,7 +91,7 @@ from 2   The Boost Distribution
 
    This is a sketch of the resulting directory structure:
    
 
    -boost_1_37_0/ .................The “boost root directory”
+boost_1_38_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:
    
 
      
-
    1. The path to the boost root directory (often /usr/local/boost_1_37_0) is
+
    2. The path to the boost root directory (often /usr/local/boost_1_38_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
      
 
      3. 
@@ -230,7 +230,7 @@ int main()
 
      Now, in the directory where you saved example.cpp, issue the
 following command:
      
 
      -c++ -I path/to/boost_1_37_0 example.cpp -o example
+c++ -I path/to/boost_1_38_0 example.cpp -o example
 
      
 
      To test the result, type:
      
 
      @@ -261,7 +261,7 @@ you'll need to acquire library binaries.
      
 
      Issue the following commands in the shell (don't type $; that
 represents the shell's prompt):
      
 
      -$ cd path/to/boost_1_37_0
+$ cd path/to/boost_1_38_0
 $ ./configure --help
 
      
 
      Select your configuration options and invoke ./configure again
@@ -428,10 +428,10 @@ bjam --build-dir=
 
      For example, your session might look like this:
      
 
      -$ cd ~/boost_1_37_0
+$ cd ~/boost_1_38_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”.
      
 
 
 
@@ -461,7 +461,7 @@ 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.
      
 
 
 
@@ -544,14 +544,14 @@ project.
 
        
 
      1. You can specify the full path to each library:
        
 
        -$ c++ -I path/to/boost_1_37_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_38_0 example.cpp -o example \
    ~/boost/lib/libboost_regex-gcc34-mt-d-1_36.a
 
        
 
        2. 
 
      2. 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_37_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_38_0 example.cpp -o example \
    -L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_36
 
        
 
        As you can see, this method is just as terse as method A for one
diff --git a/getting_started/windows.html b/getting_started/windows.html
index a5cd5f6..1face1f 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -72,7 +72,7 @@ least install the Static Multithreaded variants of the boost_1_37_0.7z or boost_1_37_0.zip and unpack it to install a complete Boost
+download boost_1_38_0.7z or boost_1_38_0.zip and unpack it to install a complete Boost
 distribution.1
        
 
 
@@ -82,7 +82,7 @@ distribution.1
 
        2   The Boost Distribution
        
 
        This is a sketch of the resulting directory structure:
        
 
        -boost_1_37_0\ .................The “boost root directory”
+boost_1_38_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -127,7 +127,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_37_0) is
+
        2. The path to the boost root directory (often C:\Program Files\boost\boost_1_38_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
          
 
          3. 
@@ -251,7 +251,7 @@ cd path\to\some\directory
 
        
 
        followed by Return.  For example,
        
 
        -cd C:\Program Files\boost\boost_1_37_0
+cd C:\Program Files\boost\boost_1_38_0
 
        
 
        Long commands can be continued across several lines by typing a
 caret (^) at the end of all but the last line.  Some examples
@@ -276,7 +276,7 @@ select Properties from the resulting pop-up menu
        
 
      3. 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_37_0
        
+
        C:\Program Files\boost\boost_1_38_0
        
 
        
 
        4. 
 
      4. In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -314,7 +314,7 @@ Visual Studio compiler.  In that window, set the  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_37_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_38_0 path\to\example.cpp
 
        
 
        To test the result, type:
        
 
        @@ -345,7 +345,7 @@ you'll need to acquire library 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_37_0\lib\.  If you installed
+boost root, typically C:\Program Files\boost\boost_1_38_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.
        
@@ -497,8 +497,8 @@ bjam --build-dir=
 
        For example, your session might look like this:4
        
 
        -C:\WINDOWS> cd C:\Program Files\boost\boost_1_37_0
-C:\Program Files\boost\boost_1_37_0> bjam ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_38_0
+C:\Program Files\boost\boost_1_38_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --toolset= --build-type=complete msvc stage
 
        
@@ -537,7 +537,7 @@ 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.
        
 
 
 
@@ -637,7 +637,7 @@ earlier:
        
 select Properties from the resulting pop-up menu
        5. 
 
      5. In Configuration Properties > Linker > Additional Library
 Directories, enter the path to the Boost binaries,
-e.g. C:\Program Files\boost\boost_1_37_0\lib\.
        6. 
+e.g. C:\Program Files\boost\boost_1_38_0\lib\.
 
      6. From the Build menu, select Build Solution.
        7. 
 
      
 
      skip to the next step
      
@@ -647,10 +647,10 @@ e.g. C:\Program For example, we can compile and link the above program from the
 Visual C++ command-line by simply adding the bold text below to
 the command line we used earlier, assuming your Boost binaries are
-in C:\Program Files\boost\boost_1_37_0\lib:
      
+in C:\Program Files\boost\boost_1_38_0\lib:
      
 
      -cl /EHsc /I path\to\boost_1_37_0 example.cpp   ^
-     /link /LIBPATH: C:\Program Files\boost\boost_1_37_0\lib
+cl /EHsc /I path\to\boost_1_38_0 example.cpp   ^
+     /link /LIBPATH: C:\Program Files\boost\boost_1_38_0\lib
 
      
 
 
      
@@ -805,7 +805,7 @@ mailing list.
      
 
    

From f53da21a9325a85352e8594cf18ea1c56e008d3d Mon Sep 17 00:00:00 2001
From: Dave Abrahams 
Date: Sun, 21 Dec 2008 01:00:33 +0000
Subject: [PATCH 07/10] Fixes #2110

[SVN r50338]
---
 getting_started/detail/library-naming.rst | 3 +--
 getting_started/unix-variants.html        | 7 +++----
 getting_started/windows.html              | 5 ++---
 3 files changed, 6 insertions(+), 9 deletions(-)

diff --git a/getting_started/detail/library-naming.rst b/getting_started/detail/library-naming.rst
index 76d99ed..9797b77 100644
--- a/getting_started/detail/library-naming.rst
+++ b/getting_started/detail/library-naming.rst
@@ -67,8 +67,7 @@ following elements:
   convention.  On most unix-style platforms the extensions are
   ``.a`` and ``.so`` for static libraries (archives) and shared
   libraries, respectively.  On Windows, ``.dll`` indicates a shared
-  library and (except for static libraries built by the ``gcc``
-  toolset_, whose names always end in ``.a``) ``.lib`` indicates a
+  library and ``.lib`` indicates a
   static or import library.  Where supported by toolsets on unix
   variants, a full version extension is added (e.g. ".so.1.34") and
   a symbolic link to the library file, named without the trailing
diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html
index f3bd8b1..4d389f7 100644
--- a/getting_started/unix-variants.html
+++ b/getting_started/unix-variants.html
@@ -431,7 +431,7 @@ bjam --build-dir=boost_1_38_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``”.
    
 
 
 
@@ -461,7 +461,7 @@ 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.
    
 
 
 
@@ -646,8 +646,7 @@ tagged as "-1_31_1".
 convention.  On most unix-style platforms the extensions are
 .a and .so for static libraries (archives) and shared
 libraries, respectively.  On Windows, .dll indicates a shared
-library and (except for static libraries built by the gcc
-    toolset, whose names always end in .a) .lib indicates a
+library and .lib indicates a
 static or import library.  Where supported by toolsets on unix
 variants, a full version extension is added (e.g. ".so.1.34") and
 a symbolic link to the library file, named without the trailing
diff --git a/getting_started/windows.html b/getting_started/windows.html
index 1face1f..41a2a7b 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -537,7 +537,7 @@ 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.
    
 
 
 
@@ -741,8 +741,7 @@ tagged as "-1_31_1".
 convention.  On most unix-style platforms the extensions are
 .a and .so for static libraries (archives) and shared
 libraries, respectively.  On Windows, .dll indicates a shared
-library and (except for static libraries built by the gcc
-toolset, whose names always end in .a) .lib indicates a
+library and .lib indicates a
 static or import library.  Where supported by toolsets on unix
 variants, a full version extension is added (e.g. ".so.1.34") and
 a symbolic link to the library file, named without the trailing

From 087b0dcd2275ee8e4c800fc7cb566c143f200e7f Mon Sep 17 00:00:00 2001
From: Dave Abrahams 
Date: Sun, 4 Jan 2009 02:18:54 +0000
Subject: [PATCH 08/10] Fixes #2622 on trunk; thanks ywu and steven. 
 Unfortunately I don't know how to move these changes to the live site

[SVN r50455]
---
 getting_started/windows.html | 4 ++--
 getting_started/windows.rst  | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/getting_started/windows.html b/getting_started/windows.html
index 41a2a7b..ed29ec8 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -500,7 +500,7 @@ bjam --build-dir=C:\Program Files\boost\boost_1_38_0
 C:\Program Files\boost\boost_1_38_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
-More? --toolset= --build-type=complete msvc stage
+More? --toolset=msvc --build-type=complete stage
 
 
    Be sure to read this note about the appearance of ^,
 More? and quotation marks (") in that line.
    
@@ -537,7 +537,7 @@ 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.
    
 
 
 
diff --git a/getting_started/windows.rst b/getting_started/windows.rst
index 6026dd7..40daf42 100644
--- a/getting_started/windows.rst
+++ b/getting_started/windows.rst
@@ -215,7 +215,7 @@ For example, your session might look like this: [#continuation]_
    C:\\WINDOWS> cd |default-root|
    |default-root|> bjam **^**
    More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^**
-   More? **--toolset=**\  **--build-type=complete** msvc stage
+   More? **--toolset=**\ msvc **--build-type=complete** stage
 
 Be sure to read `this note`__ about the appearance of ``^``,
 ``More?`` and quotation marks (``"``) in that line.

From 90d0ac022ff8ef2c39d73cfac1652d047afe4b84 Mon Sep 17 00:00:00 2001
From: Dave Abrahams 
Date: Tue, 27 Jan 2009 19:51:20 +0000
Subject: [PATCH 09/10] Merged back from release branch.

Fix up windows doc error


[SVN r50810]
---
 getting_started/unix-variants.html | 4 ++--
 getting_started/windows.html       | 2 +-
 getting_started/windows.rst        | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html
index 4d389f7..c7ab161 100644
--- a/getting_started/unix-variants.html
+++ b/getting_started/unix-variants.html
@@ -431,7 +431,7 @@ bjam --build-dir=boost_1_38_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”.
    
 
 
 
@@ -461,7 +461,7 @@ 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.
    
 
 
 
diff --git a/getting_started/windows.html b/getting_started/windows.html
index ed29ec8..94f38ed 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -500,7 +500,7 @@ bjam --build-dir=    C:\Program Files\boost\boost_1_38_0
 C:\Program Files\boost\boost_1_38_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
-More? --toolset=msvc --build-type=complete stage
+More? --build-type=complete msvc stage
 
 
    Be sure to read this note about the appearance of ^,
 More? and quotation marks (") in that line.
    
diff --git a/getting_started/windows.rst b/getting_started/windows.rst
index 40daf42..c781030 100644
--- a/getting_started/windows.rst
+++ b/getting_started/windows.rst
@@ -215,7 +215,7 @@ For example, your session might look like this: [#continuation]_
    C:\\WINDOWS> cd |default-root|
    |default-root|> bjam **^**
    More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^**
-   More? **--toolset=**\ msvc **--build-type=complete** stage
+   More? **--build-type=complete** **msvc** stage
 
 Be sure to read `this note`__ about the appearance of ``^``,
 ``More?`` and quotation marks (``"``) in that line.

From 84393b5ce2b86a09aa1ca4489ee3ce1e19fc6d3d Mon Sep 17 00:00:00 2001
From: Beman Dawes 
Date: Tue, 10 Feb 2009 13:59:38 +0000
Subject: [PATCH 10/10] Update version number to 1.38.0

[SVN r51179]
---
 getting_started/detail/release-variables.rst |  6 ++---
 getting_started/unix-variants.html           | 18 ++++++-------
 getting_started/windows.html                 | 28 ++++++++++----------
 3 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/getting_started/detail/release-variables.rst b/getting_started/detail/release-variables.rst
index 384d7a8..3f7fe8f 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.38.0
-.. |boost_ver| replace:: ``boost_1_38_0``
-.. |boost_ver-bold| replace:: **boost_1_38_0**
+.. |boost-version-number| replace:: 1.39.0
+.. |boost_ver| replace:: ``boost_1_39_0``
+.. |boost_ver-bold| replace:: **boost_1_39_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 c7ab161..819b6d1 100644
--- a/getting_started/unix-variants.html
+++ b/getting_started/unix-variants.html
@@ -63,12 +63,12 @@
 
    The most reliable way to get a copy of Boost is to download a
 distribution from SourceForge:
    
 
      
-
    1. Download boost_1_38_0.tar.bz2.
      
+
    2. Download boost_1_39_0.tar.bz2.
      
 
      3. 
 
    3. In the directory where you want to put the Boost installation,
 execute
      
 
      -tar --bzip2 -xf /path/to/boost_1_38_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_39_0.tar.bz2
 
      
 
      4. 
 
    
@@ -91,7 +91,7 @@ from 2   The Boost Distribution
 
    This is a sketch of the resulting directory structure:
    
 
    -boost_1_38_0/ .................The “boost root directory”
+boost_1_39_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:
    
 
      
-
    1. The path to the boost root directory (often /usr/local/boost_1_38_0) is
+
    2. The path to the boost root directory (often /usr/local/boost_1_39_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
      
 
      3. 
@@ -230,7 +230,7 @@ int main()
 
      Now, in the directory where you saved example.cpp, issue the
 following command:
      
 
      -c++ -I path/to/boost_1_38_0 example.cpp -o example
+c++ -I path/to/boost_1_39_0 example.cpp -o example
 
      
 
      To test the result, type:
      
 
      @@ -261,7 +261,7 @@ you'll need to acquire library binaries.
      
 
      Issue the following commands in the shell (don't type $; that
 represents the shell's prompt):
      
 
      -$ cd path/to/boost_1_38_0
+$ cd path/to/boost_1_39_0
 $ ./configure --help
 
      
 
      Select your configuration options and invoke ./configure again
@@ -428,7 +428,7 @@ bjam --build-dir=
 
      For example, your session might look like this:
      
 
      -$ cd ~/boost_1_38_0
+$ cd ~/boost_1_39_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”.
      
@@ -544,14 +544,14 @@ project.
 
        
 
      1. You can specify the full path to each library:
        
 
        -$ c++ -I path/to/boost_1_38_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_39_0 example.cpp -o example \
    ~/boost/lib/libboost_regex-gcc34-mt-d-1_36.a
 
        
 
        2. 
 
      2. 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_38_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_39_0 example.cpp -o example \
    -L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_36
 
        
 
        As you can see, this method is just as terse as method A for one
diff --git a/getting_started/windows.html b/getting_started/windows.html
index 94f38ed..4cec250 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -72,7 +72,7 @@ least install the Static Multithreaded variants of the boost_1_38_0.7z or boost_1_38_0.zip and unpack it to install a complete Boost
+download boost_1_39_0.7z or boost_1_39_0.zip and unpack it to install a complete Boost
 distribution.1
        
 
 
@@ -82,7 +82,7 @@ distribution.1
 
        2   The Boost Distribution
        
 
        This is a sketch of the resulting directory structure:
        
 
        -boost_1_38_0\ .................The “boost root directory”
+boost_1_39_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -127,7 +127,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_38_0) is
+
        2. The path to the boost root directory (often C:\Program Files\boost\boost_1_39_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
          
 
          3. 
@@ -251,7 +251,7 @@ cd path\to\some\directory
 
        
 
        followed by Return.  For example,
        
 
        -cd C:\Program Files\boost\boost_1_38_0
+cd C:\Program Files\boost\boost_1_39_0
 
        
 
        Long commands can be continued across several lines by typing a
 caret (^) at the end of all but the last line.  Some examples
@@ -276,7 +276,7 @@ select Properties from the resulting pop-up menu
        
 
      3. 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_38_0
        
+
        C:\Program Files\boost\boost_1_39_0
        
 
        
 
        4. 
 
      4. In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -314,7 +314,7 @@ Visual Studio compiler.  In that window, set the  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_38_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_39_0 path\to\example.cpp
 
        
 
        To test the result, type:
        
 
        @@ -345,7 +345,7 @@ you'll need to acquire library 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_38_0\lib\.  If you installed
+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
 step.  Otherwise, please run the installer again and install them
 now.
        
@@ -497,8 +497,8 @@ bjam --build-dir=
 
        For example, your session might look like this:4
        
 
        -C:\WINDOWS> cd C:\Program Files\boost\boost_1_38_0
-C:\Program Files\boost\boost_1_38_0> bjam ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_39_0
+C:\Program Files\boost\boost_1_39_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --build-type=complete msvc stage
 
        
@@ -637,7 +637,7 @@ earlier:
        
 select Properties from the resulting pop-up menu
        5. 
 
      5. In Configuration Properties > Linker > Additional Library
 Directories, enter the path to the Boost binaries,
-e.g. C:\Program Files\boost\boost_1_38_0\lib\.
        6. 
+e.g. C:\Program Files\boost\boost_1_39_0\lib\.
 
      6. From the Build menu, select Build Solution.
        7. 
 
      
 
      skip to the next step
      
@@ -647,10 +647,10 @@ e.g. C:\Program For example, we can compile and link the above program from the
 Visual C++ command-line by simply adding the bold text below to
 the command line we used earlier, assuming your Boost binaries are
-in C:\Program Files\boost\boost_1_38_0\lib:
      
+in C:\Program Files\boost\boost_1_39_0\lib:
      
 
      -cl /EHsc /I path\to\boost_1_38_0 example.cpp   ^
-     /link /LIBPATH: C:\Program Files\boost\boost_1_38_0\lib
+cl /EHsc /I path\to\boost_1_39_0 example.cpp   ^
+     /link /LIBPATH: C:\Program Files\boost\boost_1_39_0\lib
 
      
 
 
      
@@ -804,7 +804,7 @@ mailing list.
      
 
    
 
 
    [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.
    
     
 
 
    [1]We recommend
-downloading boost_1_37_0.7z and using 7-Zip to decompress
+downloading boost_1_38_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.
    
 
 
    [1]We recommend
-downloading boost_1_38_0.7z and using 7-Zip to decompress
+downloading boost_1_39_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.