From 2145bd13d95cb5c078cd8e686b49988ecea1d282 Mon Sep 17 00:00:00 2001 From: Beman Dawes Date: Mon, 3 Nov 2008 15:50:31 +0000 Subject: [PATCH] Prep for 1.38.0 [SVN r49564] --- getting_started/detail/release-variables.rst | 6 ++-- getting_started/unix-variants.html | 22 +++++++------- getting_started/windows.html | 30 ++++++++++---------- 3 files changed, 29 insertions(+), 29 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 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. 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
@@ -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.
    
 
 
 [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.