From 155c6c762efce00dffa3957e9040894b4ca6b68e Mon Sep 17 00:00:00 2001 From: Daniel James Date: Sun, 2 Oct 2016 22:59:15 +0100 Subject: [PATCH] Build getting started docs for new version. --- getting_started/unix-variants.html | 22 +++++++++++----------- getting_started/windows.html | 26 +++++++++++++------------- 2 files changed, 24 insertions(+), 24 deletions(-) diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html index 78115cc..87a29b0 100644 --- a/getting_started/unix-variants.html +++ b/getting_started/unix-variants.html @@ -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_62_0.tar.bz2.

    +

  2. Download boost_1_63_0.tar.bz2.

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

    -tar --bzip2 -xf /path/to/boost_1_62_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_63_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_62_0/ .................The “boost root directory”
+boost_1_63_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_62_0) is
+
  2. The path to the boost root directory (often /usr/local/boost_1_63_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
    
 
    3. 
@@ -245,7 +245,7 @@ int main()
 
    Now, in the directory where you saved example.cpp, issue the
 following command:
    
 
    -c++ -I path/to/boost_1_62_0 example.cpp -o example
+c++ -I path/to/boost_1_63_0 example.cpp -o example
 
    
 
    To test the result, type:
    
 
    @@ -276,7 +276,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_62_0
+$ cd path/to/boost_1_63_0
 $ ./bootstrap.sh --help
 
    
 
    Select your configuration options and invoke ./bootstrap.sh again
@@ -425,7 +425,7 @@ b2 --build-dir=b
 please see the Boost.Build documentation.
    
 
    For example, your session might look like this:
    
 
    -$ cd ~/boost_1_62_0
+$ cd ~/boost_1_63_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”.
    
@@ -541,14 +541,14 @@ project.
 
      
 
    1. You can specify the full path to each library:
      
 
      -$ c++ -I path/to/boost_1_62_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_63_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_62_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_63_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 49ea326..13f5ef9 100644
--- a/getting_started/windows.html
+++ b/getting_started/windows.html
@@ -61,7 +61,7 @@ not supported—they may or may not work.
      
 
      
 
      1   Get Boost
      
 
      The most reliable way to get a copy of Boost is to
-download boost_1_62_0.7z or boost_1_62_0.zip and unpack it to install a complete Boost
+download boost_1_63_0.7z or boost_1_63_0.zip and unpack it to install a complete Boost
 distribution.1
      
 
 
@@ -71,7 +71,7 @@ distribution.1
 
      2   The Boost Distribution
      
 
      This is a sketch of the resulting directory structure:
      
 
      -boost_1_62_0\ .................The “boost root directory”
+boost_1_63_0\ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost\ .........................All Boost Header files
    lib\ .....................precompiled library binaries
@@ -116,7 +116,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_62_0) is
+
      2. The path to the boost root directory (often C:\Program Files\boost\boost_1_63_0) is
 sometimes referred to as $BOOST_ROOT in documentation and
 mailing lists .
        
 
        3. 
@@ -255,7 +255,7 @@ cd path\to\some\directory
 
    
 
    followed by Return.  For example,
    
 
    -cd C:\Program Files\boost\boost_1_62_0
+cd C:\Program Files\boost\boost_1_63_0
 
    
 
    Long commands can be continued across several lines by typing a
 caret (^) at the end of all but the last line.  Some examples
@@ -280,7 +280,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_62_0
    
+
    C:\Program Files\boost\boost_1_63_0
    
 
    
 
    4. 
 
  4. In Configuration Properties > C/C++ > Precompiled Headers, change
@@ -318,7 +318,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_62_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_63_0 path\to\example.cpp
 
    
 
    To test the result, type:
    
 
    @@ -487,8 +487,8 @@ b2 --build-dir=b
 please see the Boost.Build documentation.
    
 
    For example, your session might look like this:3
    
 
    -C:\WINDOWS> cd C:\Program Files\boost\boost_1_62_0
-C:\Program Files\boost\boost_1_62_0> b2 ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_63_0
+C:\Program Files\boost\boost_1_63_0> b2 ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --build-type=complete msvc stage
 
    
@@ -627,7 +627,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_62_0\lib\.
    6. 
+e.g. C:\Program Files\boost\boost_1_63_0\lib\.
 
  6. From the Build menu, select Build Solution.
    7. 
 

 
skip to the next step

@@ -637,10 +637,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_62_0\lib:

+in C:\Program Files\boost\boost_1_63_0\lib:

 
-cl /EHsc /I path\to\boost_1_62_0 example.cpp   ^
-     /link /LIBPATH:C:\Program Files\boost\boost_1_62_0\lib
+cl /EHsc /I path\to\boost_1_63_0 example.cpp   ^
+     /link /LIBPATH:C:\Program Files\boost\boost_1_63_0\lib
 

 
 

@@ -796,7 +796,7 @@ mailing list.

 
 
 [1]We recommend
-downloading boost_1_62_0.7z and using 7-Zip to decompress
+downloading boost_1_63_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.