diff --git a/getting_started/detail/build-from-source-tail.rst b/getting_started/detail/build-from-source-tail.rst index 0168c34..78035c3 100644 --- a/getting_started/detail/build-from-source-tail.rst +++ b/getting_started/detail/build-from-source-tail.rst @@ -3,8 +3,9 @@ .. file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) Building the special ``stage`` target places Boost -library binaries in the ``stage``\ |/|\ ``lib``\ |/| subdirectory of your `build -directory`_. +library binaries in the ``stage``\ |/|\ ``lib``\ |/| subdirectory of +the Boost tree. To use a different directory pass the +``--stagedir=``\ *directory* option to ``bjam``. .. Note:: ``bjam`` is case-sensitive; it is important that all the parts shown in **bold** type above be entirely lower-case. diff --git a/getting_started/detail/header-only.rst b/getting_started/detail/header-only.rst index d26168e..d70fd2c 100644 --- a/getting_started/detail/header-only.rst +++ b/getting_started/detail/header-only.rst @@ -20,7 +20,9 @@ Boost?” The good news is that often, there's nothing to build. The only Boost libraries that *must* be built separately are: * Boost.Filesystem_ +* Boost.GraphParallel_ * Boost.IOStreams_ +* Boost.MPI_ * Boost.ProgramOptions_ * Boost.Python_ (see the `Boost.Python build documentation`__ before building and installing it) @@ -42,6 +44,12 @@ A few libraries have optional separately-compiled binaries: * Boost.Graph_ also has a binary component that is only needed if you intend to `parse GraphViz files`__. +* Boost.Math_ has binary components for the TR1 and C99 + cmath functions. + +* Boost.Random_ has a binary component which is only needed if + you're using ``random_device``. + * Boost.Test_ can be used in “header-only” or “separately compiled” mode, although **separate compilation is recommended for serious use**. diff --git a/getting_started/detail/links.rst b/getting_started/detail/links.rst index 56e6fe9..d760294 100644 --- a/getting_started/detail/links.rst +++ b/getting_started/detail/links.rst @@ -5,9 +5,13 @@ .. _Boost.DateTime: ../../libs/date_time/index.html .. _Boost.Filesystem: ../../libs/filesystem/index.html .. _Boost.Graph: ../../libs/graph/index.html +.. _Boost.GraphParallel: ../../libs/graph_parallel/index.html .. _Boost.IOStreams: ../../libs/iostreams/index.html +.. _Boost.Math: ../../libs/math/index.html +.. _Boost.MPI: ../../libs/mpi/index.html .. _Boost.ProgramOptions: ../../libs/program_options/index.html .. _Boost.Python: ../../libs/python/doc/building.html +.. _Boost.Random: ../../libs/random/index.html .. _Boost.Regex: ../../libs/regex/index.html .. _Boost.Serialization: ../../libs/serialization/index.html .. _Boost.Signals: ../../libs/signals/index.html diff --git a/getting_started/index.html b/getting_started/index.html index 3722fe7..2dacec0 100644 --- a/getting_started/index.html +++ b/getting_started/index.html @@ -2,15 +2,21 @@
+ - +The only Boost libraries that must be built separately are:
to install somewhere else. Also, consider using the ---show-libraries and --with-library_name options to limit the +--show-libraries and --with-libraries=library-name-list options to limit the long wait you'll experience if you build everything. Finally,
$ ./bjam install @@ -442,8 +454,9 @@ $ bjam --build-dir=/tmp/build-boost toolset=gcBuilding the special stage target places Boost -library binaries in the stage/lib/ subdirectory of your build -directory.
+library binaries in the stage/lib/ subdirectory of +the Boost tree. To use a different directory pass the +--stagedir=directory option to bjam.+Note
bjam is case-sensitive; it is important that all the @@ -804,6 +817,8 @@ recommend it.
The only Boost libraries that must be built separately are:
Building the special stage target places Boost -library binaries in the stage\lib\ subdirectory of your build -directory.
+library binaries in the stage\lib\ subdirectory of +the Boost tree. To use a different directory pass the +--stagedir=directory option to bjam.Note
bjam is case-sensitive; it is important that all the @@ -670,7 +677,7 @@ the command line we used earlier, assuming your Boost binaries are in C:\Program Files\boost\boost_1_44_0\lib:
cl /EHsc /I path\to\boost_1_44_0 example.cpp ^ - /link /LIBPATH: C:\Program Files\boost\boost_1_44_0\lib + /link /LIBPATH:C:\Program Files\boost\boost_1_44_0\lib