From b0f13e34f96f09421623c8ce838d9f83de6502d9 Mon Sep 17 00:00:00 2001 From: Daniel James Date: Mon, 18 Dec 2017 16:59:07 +0000 Subject: Bump to 1.67.0 --- more/getting_started/unix-variants.html | 46 ++++++++++++++++----------------- 1 file changed, 23 insertions(+), 23 deletions(-) (limited to 'more/getting_started/unix-variants.html') diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index 1b2f88e216..dcb622e29e 100644 --- a/more/getting_started/unix-variants.html +++ b/more/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_66_0.tar.bz2.

    +

  2. Download boost_1_67_0.tar.bz2.

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

    -tar --bzip2 -xf /path/to/boost_1_66_0.tar.bz2
+tar --bzip2 -xf /path/to/boost_1_67_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_66_0/ .................The “boost root directory”
+boost_1_67_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_66_0) is +

  2. The path to the boost root directory (often /usr/local/boost_1_67_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_66_0 example.cpp -o example
+c++ -I path/to/boost_1_67_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_66_0
+$ cd path/to/boost_1_67_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_66_0
+$ cd ~/boost_1_67_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_66_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_67_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_66_0 example.cpp -o example \
+$ c++ -I path/to/boost_1_67_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!

      -- cgit v1.2.1