diff --git a/getting_started/detail/release-variables.rst b/getting_started/detail/release-variables.rst index a90a5f1..97b2567 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:: 67 -.. |boost_ver| replace:: ``boost_1_67_0`` -.. |boost_ver-bold| replace:: **boost_1_67_0** +.. |boost-version-number| replace:: 66 +.. |boost_ver| replace:: ``boost_1_66_0`` +.. |boost_ver-bold| replace:: **boost_1_66_0** -.. _sf-download: http://www.boost.org/users/history/version_1_67_0.html +.. _sf-download: http://www.boost.org/users/history/version_1_66_0.html diff --git a/getting_started/index.html b/getting_started/index.html index 90db3cb..6358b39 100644 --- a/getting_started/index.html +++ b/getting_started/index.html @@ -3,7 +3,7 @@ - + Boost Getting Started @@ -14,7 +14,7 @@ -
+

Use the latest version of this Getting Started guide

The Boost website version of this Getting Started guide may have updated information, such as the location of additional installers diff --git a/getting_started/unix-variants.html b/getting_started/unix-variants.html index dcb622e..1b2f88e 100644 --- a/getting_started/unix-variants.html +++ b/getting_started/unix-variants.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Unix Variants @@ -61,18 +61,18 @@

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

    +

  2. Download boost_1_66_0.tar.bz2.

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

    -tar --bzip2 -xf /path/to/boost_1_67_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_66_0.tar.bz2
-
+

Other Packages

RedHat, Debian, and other distribution packagers supply Boost library packages, however you may need to adapt these @@ -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,10 +91,10 @@ from 2   The Boost Distribution

This is a sketch of the resulting directory structure:

-boost_1_67_0/ .................The “boost root directory”
+boost_1_66_0/ .................The “boost root directory”
    index.htm .........A copy of www.boost.org starts here
    boost/ .........................All Boost Header files
-   
+    
    libs/ ............Tests, .cpps, docs, etc., by library
      index.html ........Library documentation starts here
      algorithm/
@@ -136,12 +136,12 @@ 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_67_0) is +

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

  3. To compile anything in Boost, you need a directory containing -the boost/ subdirectory in your #include path.

    +the boost/ subdirectory in your #include path.

  4. Since all of Boost's header files have the .hpp extension, and live in the boost/ subdirectory of the boost root, your @@ -154,7 +154,7 @@ Boost #include directives will look like:

    #include "boost/whatever.hpp"

    depending on your preference regarding the use of angle bracket -includes.

    +includes.

  5. Don't be distracted by the doc/ subdirectory; it only contains a subset of the Boost documentation. Start with @@ -169,7 +169,7 @@ contains a subset of the Boost documentation. Start with

    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.

    -
    +

    Nothing to Build?

    Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and @@ -246,7 +246,7 @@ int main()

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

    -c++ -I path/to/boost_1_67_0 example.cpp -o example
+c++ -I path/to/boost_1_66_0 example.cpp -o example

    To test the result, type:

    @@ -277,7 +277,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_67_0
+$ cd path/to/boost_1_66_0
 $ ./bootstrap.sh --help
 
    
 
    Select your configuration options and invoke ./bootstrap.sh again
@@ -328,7 +328,7 @@ the directory where you want Boost.Build to be installed

    6. First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).

    -
    +

    Note

    If you previously chose a toolset for the purposes of building b2, you should assume it won't work and instead @@ -405,7 +405,7 @@ the Apache standard library in C++03 mode use

    If you have multiple versions of a particular compiler installed, you can append the version number to the toolset name, preceded by a hyphen, e.g. intel-9.0 or -borland-5.4.3.

    +borland-5.4.3.

    5.2.3   Select a Build Directory

    @@ -420,13 +420,13 @@ purpose in your current working directory.

    Change your current directory to the Boost root directory and invoke b2 as follows:

    -b2 --build-dir=build-directory toolset=toolset-name  stage
+b2 --build-dir=build-directory toolset=toolset-name   stage

    For a complete description of these and other invocation options, please see the Boost.Build documentation.

    For example, your session might look like this:

    -$ cd ~/boost_1_67_0
+$ cd ~/boost_1_66_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”.

    @@ -437,7 +437,7 @@ $ b2 --build-dir=/tmp/build-boost toolset=gcc library binaries in the stage/lib/ subdirectory of the Boost tree. To use a different directory pass the --stagedir=directory option to b2.

    -
    +

    Note

    b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.

    @@ -455,7 +455,7 @@ be interested in:

  6. choosing a specific build variant by adding release or debug to the command line.
    7. -
    +

    Note

    Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure @@ -542,14 +542,14 @@ project.

    1. You can specify the full path to each library:

      -$ c++ -I path/to/boost_1_67_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_66_0 example.cpp -o example \
    ~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a

    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_67_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_66_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 @@ -785,7 +785,7 @@ mailing list.

    3. Boost.Build mailing list
    4. Index of all Boost library documentation
      5. -
      +

      Onward

      Good luck, and have fun!

      diff --git a/getting_started/windows.html b/getting_started/windows.html index eca8217..c2196c3 100644 --- a/getting_started/windows.html +++ b/getting_started/windows.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Windows @@ -14,7 +14,7 @@ -
      +

      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 @@ -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_67_0.7z or boost_1_67_0.zip and unpack it to install a complete Boost +download boost_1_66_0.7z or boost_1_66_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_67_0\ .................The “boost root directory”
+boost_1_66_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_67_0) is +

      2. The path to the boost root directory (often C:\Program Files\boost\boost_1_66_0) is sometimes referred to as $BOOST_ROOT in documentation and mailing lists .

        3. @@ -154,7 +154,7 @@ contains a subset of the Boost documentation. Start with

        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.

        -
        +

        Nothing to Build?

        Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and @@ -228,7 +228,7 @@ int main() }

        Copy the text of this program into a file called example.cpp.

        -
        +

        Note

        To build the examples in this guide, you can use an Integrated Development Environment (IDE) like Visual Studio, or @@ -256,7 +256,7 @@ cd path\to\some\directory

        followed by Return. For example,

        -cd C:\Program Files\boost\boost_1_67_0
+cd C:\Program Files\boost\boost_1_66_0

        Long commands can be continued across several lines by typing a caret (^) at the end of all but the last line. Some examples @@ -281,7 +281,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_67_0

        +

        C:\Program Files\boost\boost_1_66_0

      4. In Configuration Properties > C/C++ > Precompiled Headers, change @@ -319,7 +319,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_67_0 path\to\example.cpp
+cl /EHsc /I path\to\boost_1_66_0 path\to\example.cpp

        To test the result, type:

        @@ -387,7 +387,7 @@ the directory where you want Boost.Build to be installed

        5. First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).

        -
        +

        Note

        If you previously chose a toolset for the purposes of building b2, you should assume it won't work and instead @@ -488,8 +488,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_67_0
-C:\Program Files\boost\boost_1_67_0> b2 ^
+C:\WINDOWS> cd C:\Program Files\boost\boost_1_66_0
+C:\Program Files\boost\boost_1_66_0> b2 ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --build-type=complete msvc stage
        @@ -506,7 +506,7 @@ list.

        library binaries in the stage\lib\ subdirectory of the Boost tree. To use a different directory pass the --stagedir=directory option to b2.

        -
        +

        Note

        b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.

        @@ -524,7 +524,7 @@ be interested in:

      5. choosing a specific build variant by adding release or debug to the command line.
        6. -
        +

        Note

        Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure @@ -607,7 +607,7 @@ build settings. whose compile configuration is compatible with the rest of your project.

      -
      +

      Auto-Linking

      Most Windows compilers and linkers have so-called “auto-linking support,” which eliminates the second challenge. Special code in @@ -628,7 +628,7 @@ earlier:

      select Properties from the resulting pop-up menu
    5. In Configuration Properties > Linker > Additional Library Directories, enter the path to the Boost binaries, -e.g. C:\Program Files\boost\boost_1_67_0\lib\.
      6. +e.g. C:\Program Files\boost\boost_1_66_0\lib\.
    6. From the Build menu, select Build Solution.

    skip to the next step

    @@ -638,15 +638,15 @@ 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_67_0\lib:

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

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

    6.3   Library Naming

    -
    +

    Note

    If, like Visual C++, your compiler supports auto-linking, you can probably skip to the next step.

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

  7. Boost.Build mailing list
  8. Index of all Boost library documentation
    9. -
    +

    Onward

    Good luck, and have fun!

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

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