Index: unix-variants.rst =================================================================== --- unix-variants.rst (revision 52397) +++ unix-variants.rst (working copy) @@ -96,16 +96,16 @@ .. parsed-literal:: **$** cd |root| - **$** ./configure --help + **$** ./bootstrap.sh --help -Select your configuration options and invoke ``./configure`` again +Select your configuration options and invoke ``./bootstrap.sh`` again without the ``--help`` option. Unless you have write permission in your system's ``/usr/local/`` directory, you'll probably want to at least use .. parsed-literal:: - **$** ./configure **--prefix=**\ *path*\ /\ *to*\ /\ *installation*\ /\ *prefix* + **$** ./bootstrap.sh **--prefix=**\ *path*\ /\ *to*\ /\ *installation*\ /\ *prefix* to install somewhere else. Also, consider using the ``--show-libraries`` and ``--with-libraries=`` options to limit the @@ -113,7 +113,7 @@ .. parsed-literal:: - **$** make install + **$** ./bjam install will leave Boost binaries in the ``lib/`` subdirectory of your installation prefix. You will also find a copy of the Boost @@ -155,7 +155,7 @@ .. parsed-literal:: $ c++ -I |root| example.cpp -o example **\\** - **~/boost/lib/libboost_regex-gcc34-mt-d-1_36.a** + **~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a** B. You can separately specify a directory to search (with ``-L``\ *directory*) and a library name to search for (with ``-l``\ @@ -165,7 +165,7 @@ .. parsed-literal:: $ c++ -I |root| example.cpp -o example **\\** - **-L~/boost/lib/ -lboost_regex-gcc34-mt-d-1_36** + **-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 library; it *really* pays off when you're using multiple Index: windows.rst =================================================================== --- windows.rst (revision 52397) +++ windows.rst (working copy) @@ -199,6 +199,24 @@ __ `Link Your Program to a Boost Library`_ +Or, Simplified Build From Source +-------------------------------- + +If you wish to build from source and is using Visual C++, you can use a +simple build procedure described in this section. Open the command prompt +and change your current directory to the Boost root directory. Then, type +the following commands:: + + bootstrap + .\bjam + +The first command prepares the Boost.Build system for use. The second +command invokes Boost.Build to build C++ Boost. Please consult the +`Boost.Build documentation`__ for a list of options that can be passed +to ``bjam``. + +__ http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html + Or, Build Binaries From Source ------------------------------ Index: detail/links.rst =================================================================== --- detail/links.rst (revision 52397) +++ detail/links.rst (working copy) @@ -11,6 +11,7 @@ .. _Boost.Regex: ../../libs/regex/index.html .. _Boost.Serialization: ../../libs/serialization/index.html .. _Boost.Signals: ../../libs/signals/index.html +.. _Boost.System: ../../libs/system/index.html .. _Boost.Test: ../../libs/test/index.html .. _Boost.Thread: ../../doc/html/thread.html .. _Boost.Wave: ../../libs/wave/index.html Index: detail/build-from-source-tail.rst =================================================================== --- detail/build-from-source-tail.rst (revision 52397) +++ detail/build-from-source-tail.rst (working copy) @@ -3,7 +3,7 @@ .. 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``\ |/| subdirectory of your `build +library binaries in the ``stage``\ |/|\ ``lib``\ |/| subdirectory of your `build directory`_. .. Note:: ``bjam`` is case-sensitive; it is important that all the Index: detail/header-only.rst =================================================================== --- detail/header-only.rst (revision 52397) +++ detail/header-only.rst (working copy) @@ -27,6 +27,7 @@ * Boost.Regex_ * Boost.Serialization_ * Boost.Signals_ +* Boost.System_ * Boost.Thread_ * Boost.Wave_