diff --git a/getting_started/detail/release-variables.rst b/getting_started/detail/release-variables.rst index dd2ba75..4f971d2 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.52.0 -.. |boost_ver| replace:: ``boost_1_52_0`` -.. |boost_ver-bold| replace:: **boost_1_52_0** +.. |boost-version-number| replace:: 1.53.0 +.. |boost_ver| replace:: ``boost_1_53_0`` +.. |boost_ver-bold| replace:: **boost_1_53_0** -.. _sf-download: http://www.boost.org/users/history/version_1_52_0.html +.. _sf-download: http://www.boost.org/users/history/version_1_53_0.html diff --git a/getting_started/index.html b/getting_started/index.html index 14a4021..f82b1e4 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 46a4221..4b3ee6d 100644 --- a/getting_started/unix-variants.html +++ b/getting_started/unix-variants.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Unix Variants @@ -61,14 +61,14 @@

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

    +

  2. Download boost_1_53_0.tar.bz2.

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

    -tar --bzip2 -xf /path/to/boost_1_52_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_53_0.tar.bz2
@@ -81,7 +81,7 @@ 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 any trouble, we suggest using an official Boost distribution -from SourceForge.

+from SourceForge.

@@ -91,7 +91,7 @@ from 2   The Boost Distribution

This is a sketch of the resulting directory structure:

-boost_1_52_0/ .................The “boost root directory”
+boost_1_53_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_52_0) is
+
  2. The path to the boost root directory (often /usr/local/boost_1_53_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
    
 
    3. 
@@ -237,7 +237,7 @@ int main()
 
    Now, in the directory where you saved example.cpp, issue the
 following command:
    
 
    -c++ -I path/to/boost_1_52_0 example.cpp -o example
+c++ -I path/to/boost_1_53_0 example.cpp -o example
 
    
 
    To test the result, type:
    
 
    @@ -268,7 +268,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_52_0
+$ cd path/to/boost_1_53_0
 $ ./bootstrap.sh --help
 
    
 
    Select your configuration options and invoke ./bootstrap.sh again
@@ -420,7 +420,7 @@ b2 --build-dir=b
 please see the Boost.Build documentation.
    
 
    For example, your session might look like this:
    
 
    -$ cd ~/boost_1_52_0
+$ cd ~/boost_1_53_0
 $ b2 --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”.
    
@@ -536,14 +536,14 @@ project.
 
      
 
    1. You can specify the full path to each library:
      
 
      -$ c++ -I path/to/boost_1_52_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_53_0 example.cpp -o example \
    ~/boost/stage/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_52_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_53_0 example.cpp -o example \
    -L~/boost/stage/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 a73d31f..e790395 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -3,7 +3,7 @@
 
 
 
-
+
 Boost Getting Started on Windows
 
 
@@ -64,7 +64,7 @@ not supported—they may or may not work.
      
 
      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
 updated information on installers as they become available, or see
-Boost downloads or the installer provided by BoostPro
+Boost downloads or the installer provided by BoostPro
 Computing.  We especially recommend using an installer if you use
 Microsoft Visual Studio, because the installer can download and
 install precompiled library binaries, saving you the trouble of
@@ -73,7 +73,7 @@ least install the Static Multithreaded variants of the boost_1_52_0.7z or boost_1_52_0.zip and unpack it to install a complete Boost
+download boost_1_53_0.7z or boost_1_53_0.zip and unpack it to install a complete Boost
 distribution.1
      
 
 
@@ -83,7 +83,7 @@ distribution.1
 
      2   The Boost Distribution
      
 
      This is a sketch of the resulting directory structure:
      
 
      -boost_1_52_0\ .................The “boost root directory”
+boost_1_53_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -128,7 +128,7 @@ anything you can use in these directories.
      
 
 
      It's important to note the following:
      
 
        
-
      1. The path to the boost root directory (often C:\Program Files\boost\boost_1_52_0) is
+
      2. The path to the boost root directory (often C:\Program Files\boost\boost_1_53_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
        
 
        3. 
@@ -259,7 +259,7 @@ cd path\to\some\directory
 
      
 
      followed by Return.  For example,
      
 
      -cd C:\Program Files\boost\boost_1_52_0
+cd C:\Program Files\boost\boost_1_53_0
 
      
 
      Long commands can be continued across several lines by typing a
 caret (^) at the end of all but the last line.  Some examples
@@ -284,7 +284,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_52_0
      
+
      C:\Program Files\boost\boost_1_53_0
      
 
      
 
      4. 
 
    4. In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -322,7 +322,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_52_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_53_0 path\to\example.cpp
 
      
 
      To test the result, type:
      
 
      @@ -353,7 +353,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_52_0\lib\.  If you installed
+boost root, typically C:\Program Files\boost\boost_1_53_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.
      
@@ -504,8 +504,8 @@ b2 --build-dir=b
 please see the Boost.Build documentation.
      
 
      For example, your session might look like this:4
      
 
      -C:\WINDOWS> cd C:\Program Files\boost\boost_1_52_0
-C:\Program Files\boost\boost_1_52_0> b2 ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_53_0
+C:\Program Files\boost\boost_1_53_0> b2 ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --build-type=complete msvc stage
 
      
@@ -644,7 +644,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_52_0\lib\.
      6. 
+e.g. C:\Program Files\boost\boost_1_53_0\lib\.
 
    6. From the Build menu, select Build Solution.
      7. 
 
    
 
    skip to the next step
    
@@ -654,10 +654,10 @@ e.g. C:\Program Files\boos
 
    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_52_0\lib:
    
+in C:\Program Files\boost\boost_1_53_0\lib:
    
 
    -cl /EHsc /I path\to\boost_1_52_0 example.cpp   ^
-     /link /LIBPATH:C:\Program Files\boost\boost_1_52_0\lib
+cl /EHsc /I path\to\boost_1_53_0 example.cpp   ^
+     /link /LIBPATH:C:\Program Files\boost\boost_1_53_0\lib
 
    
 
 
    
@@ -813,7 +813,7 @@ mailing list.
    
 
 
 [1]We recommend
-downloading boost_1_52_0.7z and using 7-Zip to decompress
+downloading boost_1_53_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.