diff --git a/more/getting_started/index.html b/more/getting_started/index.html index 2f60d00baa..07428bdf08 100644 --- a/more/getting_started/index.html +++ b/more/getting_started/index.html @@ -14,6 +14,13 @@ +
+

Use the latest version of this Getting Started guide

+

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 to the Boost libraries! By the time you've completed this diff --git a/more/getting_started/index.rst b/more/getting_started/index.rst index 23bfa7bd0b..d12b400670 100644 --- a/more/getting_started/index.rst +++ b/more/getting_started/index.rst @@ -12,6 +12,16 @@ __ ../../index.htm +.. Admonition:: Use the latest version of this Getting Started guide + + 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. + + .. _`Boost website version of this Getting Started guide`: + http://www.boost.org/doc/libs/1_36_0/more/getting_started/index.html + Welcome ------- diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index 91a29ff9af..0830ef15f8 100644 --- a/more/getting_started/unix-variants.html +++ b/more/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_35_0.tar.bz2.

    +

  2. Download boost_1_36_0.tar.bz2.

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

    -tar --bzip2 -xf /path/to/boost_1_35_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_36_0.tar.bz2
@@ -91,7 +91,7 @@ from 2   The Boost Distribution

This is a sketch of the resulting directory structure:

-boost_1_35_0/ .................The “boost root directory”
+boost_1_36_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_35_0) is +

  2. The path to the boost root directory (often /usr/local/boost_1_36_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_35_0 example.cpp -o example
+c++ -I path/to/boost_1_36_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_35_0
+$ cd path/to/boost_1_36_0
 $ ./configure --help
 
    
 
    Select your configuration options and invoke ./configure again
@@ -425,9 +425,14 @@ bjam --build-dir=
 
    For example, your session might look like this:
    
 
    -$ cd ~/boost_1_35_0
+$ cd ~/boost_1_36_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
+$ bjam --build-dir=/tmp/build-boost --toolset=gcc --build-type=complete stage
+
    
 
 
 
@@ -533,15 +538,15 @@ project.
 
      
 
    1. You can specify the full path to each library:
      
 
      -$ c++ -I path/to/boost_1_35_0 example.cpp -o example \
-   ~/boost/lib/libboost_regex-gcc34-mt-d-1_35.a
+$ c++ -I path/to/boost_1_36_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_35_0 example.cpp -o example \
-   -L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_35
+$ c++ -I path/to/boost_1_36_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
 library; it really pays off when you're using multiple
diff --git a/more/getting_started/unix-variants.rst b/more/getting_started/unix-variants.rst
index c8b1db13b9..0a734e034f 100644
--- a/more/getting_started/unix-variants.rst
+++ b/more/getting_started/unix-variants.rst
@@ -142,6 +142,13 @@ 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
+
 .. include:: detail/build-from-source-tail.rst
 
 .. include:: detail/link-head.rst
diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html
index 32d61f77d3..beb71e6465 100644
--- a/more/getting_started/windows.html
+++ b/more/getting_started/windows.html
@@ -69,7 +69,7 @@ them yourself.  To complete this tutorial, you'll need to at least
 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_35_0.exe and run it to install a complete Boost
+download boost_1_36_0.exe and run it to install a complete Boost
 distribution.1
      
 
 
@@ -79,7 +79,7 @@ distribution.1
 
      2   The Boost Distribution
      
 
      This is a sketch of the resulting directory structure:
      
 
      -boost_1_35_0\ .................The “boost root directory”
+boost_1_36_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -124,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_35_0) is
+
      2. The path to the boost root directory (often C:\Program Files\boost\boost_1_36_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
        
 
        3. 
@@ -248,7 +248,7 @@ cd path\to\some\directory
 
      
 
      followed by Return.  For example,
      
 
      -cd C:\Program Files\boost\boost_1_35_0
+cd C:\Program Files\boost\boost_1_36_0
 
      
 
      Long commands can be continued across several lines by typing a
 caret (^) at the end of all but the last line.  Some examples
@@ -273,7 +273,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_35_0
      
+
      C:\Program Files\boost\boost_1_36_0
      
 
      
 
      4. 
 
    4. In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -311,7 +311,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_35_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_36_0 path\to\example.cpp
 
      
 
      To test the result, type:
      
 
      @@ -342,7 +342,7 @@ you'll need to acquire library binaries.
      
 
      5.1   Install Visual Studio (2005 or .NET 2003) Binaries
      
 
      The installer supplied by Boost Consulting will download and
 install pre-compiled binaries into the lib\ subdirectory of the
-boost root, typically C:\Program Files\boost\boost_1_35_0\lib\.  If you installed
+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
 step.  Otherwise, please run the installer again and install them
 now.
      
@@ -491,8 +491,8 @@ bjam --build-dir=
 
      For example, your session might look like this:4
      
 
      -C:\WINDOWS> cd C:\Program Files\boost\boost_1_35_0
-C:\Program Files\boost\boost_1_35_0> bjam ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_36_0
+C:\Program Files\boost\boost_1_36_0> bjam ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --toolset=msvc stage
 
      
@@ -620,7 +620,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_35_0\lib\.
      6. 
+e.g. C:\Program Files\boost\boost_1_36_0\lib\.
 
    6. From the Build menu, select Build Solution.
      7. 
 
    
 
    skip to the next step
    
@@ -630,10 +630,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_35_0\lib:
    
+in C:\Program Files\boost\boost_1_36_0\lib:
    
 
    -cl /EHsc /I path\to\boost_1_35_0 example.cpp   ^
-     /link /LIBPATH: C:\Program Files\boost\boost_1_35_0\lib
+cl /EHsc /I path\to\boost_1_36_0 example.cpp   ^
+     /link /LIBPATH: C:\Program Files\boost\boost_1_36_0\lib
 
    
 
 
    
@@ -788,7 +788,7 @@ mailing list.
    
 
 
 [1]If you prefer not to download executable programs,
-download boost_1_35_0.zip and use an external tool to decompress
+download boost_1_36_0.zip and use an external tool to decompress
 it.  We don't recommend using Windows' built-in decompression as
 it can be painfully slow for large archives.