From e47f34f24fc66f5295fcc747a5bf86ddfa96dcb5 Mon Sep 17 00:00:00 2001 From: Vladimir Prus Date: Sun, 3 Jul 2011 08:08:57 +0000 Subject: Merge Boost.Build branding changes: https://svn.boost.org/trac/boost/changeset/72773 https://svn.boost.org/trac/boost/changeset/72793 Authorized by Beman. [SVN r72866] --- .../detail/build-from-source-head.rst | 12 ++++---- .../detail/build-from-source-tail.rst | 8 +++--- more/getting_started/detail/distro.rst | 2 +- more/getting_started/unix-variants.html | 28 +++++++++---------- more/getting_started/unix-variants.rst | 4 +-- more/getting_started/windows.html | 32 +++++++++++----------- more/getting_started/windows.rst | 8 +++--- 7 files changed, 47 insertions(+), 47 deletions(-) (limited to 'more') diff --git a/more/getting_started/detail/build-from-source-head.rst b/more/getting_started/detail/build-from-source-head.rst index 4d63c08843..d1bb9c240b 100644 --- a/more/getting_started/detail/build-from-source-head.rst +++ b/more/getting_started/detail/build-from-source-head.rst @@ -11,7 +11,7 @@ install it. To do this: 1. Go to the directory ``tools``\ |/|\ ``build``\ |/|\ ``v2``\ |/|. 2. Run ``bootstrap.bat`` -3. Run ``bjam install --prefix=``\ *PREFIX* where *PREFIX* is +3. Run ``b2 install --prefix=``\ *PREFIX* where *PREFIX* is the directory where you want Boost.Build to be installed 4. Add *PREFIX*\ |/|\ ``bin`` to your PATH environment variable. @@ -31,10 +31,10 @@ Boost.Build documentation`__). __ http://www.boost.org/boost-build2/doc/html/bbv2/reference/tools.html .. Note:: If you previously chose a toolset for the purposes of - `building bjam`_, you should assume it won't work and instead + `building b2`_, you should assume it won't work and instead choose newly from the table below. -.. _building bjam: ../../doc/html/bbv2/installation.html +.. _building b2: ../../doc/html/bbv2/installation.html +-----------+--------------------+-----------------------------+ |Toolset |Vendor |Notes | @@ -102,18 +102,18 @@ directory is writable, this step isn't strictly necessary: by default Boost.Build will create a ``bin.v2/`` subdirectory for that purpose in your current working directory. -Invoke ``bjam`` +Invoke ``b2`` ............... .. |build-directory| replace:: *build-directory* .. |toolset-name| replace:: *toolset-name* Change your current directory to the Boost root directory and -invoke ``bjam`` as follows: +invoke ``b2`` as follows: .. parsed-literal:: - bjam **--build-dir=**\ |build-directory|_ **toolset=**\ |toolset-name|_ |build-type-complete| stage + b2 **--build-dir=**\ |build-directory|_ **toolset=**\ |toolset-name|_ |build-type-complete| stage For a complete description of these and other invocation options, please see the `Boost.Build documentation`__. diff --git a/more/getting_started/detail/build-from-source-tail.rst b/more/getting_started/detail/build-from-source-tail.rst index 78035c3c7b..dd782ac6c5 100644 --- a/more/getting_started/detail/build-from-source-tail.rst +++ b/more/getting_started/detail/build-from-source-tail.rst @@ -5,15 +5,15 @@ Building the special ``stage`` target places Boost library binaries in the ``stage``\ |/|\ ``lib``\ |/| subdirectory of the Boost tree. To use a different directory pass the -``--stagedir=``\ *directory* option to ``bjam``. +``--stagedir=``\ *directory* option to ``b2``. -.. Note:: ``bjam`` is case-sensitive; it is important that all the +.. Note:: ``b2`` is case-sensitive; it is important that all the parts shown in **bold** type above be entirely lower-case. For a description of other options you can pass when invoking -``bjam``, type:: +``b2``, type:: - bjam --help + b2 --help In particular, to limit the amount of time spent building, you may be interested in: diff --git a/more/getting_started/detail/distro.rst b/more/getting_started/detail/distro.rst index 708dfd1ab6..939efe2609 100644 --- a/more/getting_started/detail/distro.rst +++ b/more/getting_started/detail/distro.rst @@ -20,7 +20,7 @@ This is a sketch of the resulting directory structure: **array**\ |//| *…more libraries…* **status**\ |//| .........................\ *Boost-wide test suite* - **tools**\ |//| ...........\ *Utilities, e.g. bjam, quickbook, bcp* + **tools**\ |//| ...........\ *Utilities, e.g. Boost.Build, quickbook, bcp* **more**\ |//| ..........................\ *Policy documents, etc.* **doc**\ |//| ...............\ *A subset of all Boost library docs* diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index 164764a3e4..3c55d77df3 100644 --- a/more/getting_started/unix-variants.html +++ b/more/getting_started/unix-variants.html @@ -43,7 +43,7 @@
  • 5.2.1   Install Boost.Build
  • 5.2.2   Identify Your Toolset
  • 5.2.3   Select a Build Directory
    • -
  • 5.2.4   Invoke bjam
    • +
  • 5.2.4   Invoke b2
  • 5.3   Expected Build Output
    • @@ -102,7 +102,7 @@ from --show-libraries and --with-libraries=library-name-list options to limit the long wait you'll experience if you build everything. Finally,

    -$ ./bjam install
+$ ./b2 install

    will leave Boost binaries in the lib/ subdirectory of your installation prefix. You will also find a copy of the Boost @@ -314,7 +314,7 @@ install it. To do this:

    1. Go to the directory tools/build/v2/.
    2. Run bootstrap.bat
      3. -
    3. Run bjam install --prefix=PREFIX where PREFIX is +
    4. Run b2 install --prefix=PREFIX where PREFIX is the directory where you want Boost.Build to be installed
    5. Add PREFIX/bin to your PATH environment variable.
    @@ -327,7 +327,7 @@ Boost.Build documentation    ).

    Note

    If you previously chose a toolset for the purposes of -building bjam, you should assume it won't work and instead +building b2, you should assume it won't work and instead choose newly from the table below.

    @@ -426,19 +426,19 @@ directory is writable, this step isn't strictly necessary: by default Boost.Build will create a bin.v2/ subdirectory for that purpose in your current working directory.

    -
    -

    5.2.4   Invoke bjam

    +
    +

    5.2.4   Invoke b2

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

    +invoke b2 as follows:

    -bjam --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_47_0
-$ bjam --build-dir=/tmp/build-boost toolset=gcc stage
+$ 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”.

    @@ -447,16 +447,16 @@ $ bjam --build-dir=/tmp/build-boost toolset=gc

    Building the special stage target places Boost library binaries in the stage/lib/ subdirectory of the Boost tree. To use a different directory pass the ---stagedir=directory option to bjam.

    +--stagedir=directory option to b2.

    Note

    -

    bjam is case-sensitive; it is important that all the +

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

    For a description of other options you can pass when invoking -bjam, type:

    +b2, type:

    -bjam --help
+b2 --help

    In particular, to limit the amount of time spent building, you may be interested in:

    diff --git a/more/getting_started/unix-variants.rst b/more/getting_started/unix-variants.rst index e80378884c..40f6f228d4 100644 --- a/more/getting_started/unix-variants.rst +++ b/more/getting_started/unix-variants.rst @@ -113,7 +113,7 @@ long wait you'll experience if you build everything. Finally, .. parsed-literal:: - **$** ./bjam install + **$** ./b2 install will leave Boost binaries in the ``lib/`` subdirectory of your installation prefix. You will also find a copy of the Boost @@ -150,7 +150,7 @@ For example, your session might look like this: .. parsed-literal:: $ cd ~/|boost_ver| - $ bjam **--build-dir=**\ /tmp/build-boost **toolset=**\ gcc stage + $ 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``”. diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html index 4e77e2c10e..3b37985270 100644 --- a/more/getting_started/windows.html +++ b/more/getting_started/windows.html @@ -42,7 +42,7 @@ not supported—they may or may not work.

  • 5.3.1   Install Boost.Build
  • 5.3.2   Identify Your Toolset
  • 5.3.3   Select a Build Directory
    • -
  • 5.3.4   Invoke bjam
    • +
  • 5.3.4   Invoke b2
  • 5.4   Expected Build Output
    • @@ -94,7 +94,7 @@ distribution.1 array\ …more libraries… status\ .........................Boost-wide test suite - tools\ ...........Utilities, e.g. bjam, quickbook, bcp + tools\ ...........Utilities, e.g. Boost.Build, quickbook, bcp more\ ..........................Policy documents, etc. doc\ ...............A subset of all Boost library docs @@ -367,12 +367,12 @@ and change your current directory to the Boost root directory. Then, type the following commands:

     bootstrap
-.\bjam
+.\b2

    The first command prepares the Boost.Build system for use. The second command invokes Boost.Build to build the separately-compiled Boost libraries. Please consult the Boost.Build documentation for a list -of options that can be passed to bjam.

    +of allowed options.

    5.3   Or, Build Binaries From Source

    @@ -395,7 +395,7 @@ install it. To do this:

    1. Go to the directory tools\build\v2\.
    2. Run bootstrap.bat
      3. -
    3. Run bjam install --prefix=PREFIX where PREFIX is +
    4. Run b2 install --prefix=PREFIX where PREFIX is the directory where you want Boost.Build to be installed
    5. Add PREFIX\bin to your PATH environment variable.
    @@ -408,7 +408,7 @@ Boost.Build documentation).

    Note

    If you previously chose a toolset for the purposes of -building bjam, you should assume it won't work and instead +building b2, you should assume it won't work and instead choose newly from the table below.

    @@ -510,25 +510,25 @@ directory is writable, this step isn't strictly necessary: by default Boost.Build will create a bin.v2/ subdirectory for that purpose in your current working directory.

    -
    -

    5.3.4   Invoke bjam

    +
    +

    5.3.4   Invoke b2

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

    +invoke b2 as follows:

    -bjam --build-dir=build-directory toolset=toolset-name --build-type=complete stage
+b2 --build-dir=build-directory toolset=toolset-name --build-type=complete 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:4

     C:\WINDOWS> cd C:\Program Files\boost\boost_1_47_0
-C:\Program Files\boost\boost_1_47_0> bjam ^
+C:\Program Files\boost\boost_1_47_0> b2 ^
 More? --build-dir="C:\Documents and Settings\dave\build-boost" ^
 More? --build-type=complete msvc stage

    Be sure to read this note about the appearance of ^, More? and quotation marks (") in that line.

    -

    The option “--build-type=complete” causes bjam to build +

    The option “--build-type=complete” causes Boost.Build to build all supported variants of the libraries. For instructions on how to build only specific variants, please ask on the Boost.Build mailing list.

    @@ -538,16 +538,16 @@ list.

    Building the special stage target places Boost library binaries in the stage\lib\ subdirectory of the Boost tree. To use a different directory pass the ---stagedir=directory option to bjam.

    +--stagedir=directory option to b2.

    Note

    -

    bjam is case-sensitive; it is important that all the +

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

    For a description of other options you can pass when invoking -bjam, type:

    +b2, type:

    -bjam --help
+b2 --help

    In particular, to limit the amount of time spent building, you may be interested in:

    diff --git a/more/getting_started/windows.rst b/more/getting_started/windows.rst index 280373cfe7..2a396a8651 100644 --- a/more/getting_started/windows.rst +++ b/more/getting_started/windows.rst @@ -208,12 +208,12 @@ and change your current directory to the Boost root directory. Then, type the following commands:: bootstrap - .\bjam + .\b2 The first command prepares the Boost.Build system for use. The second command invokes Boost.Build to build the separately-compiled Boost libraries. Please consult the `Boost.Build documentation`__ for a list -of options that can be passed to ``bjam``. +of allowed options. __ http://www.boost.org/boost-build2/doc/html/bbv2/overview/invocation.html @@ -239,14 +239,14 @@ For example, your session might look like this: [#continuation]_ .. parsed-literal:: C:\\WINDOWS> cd |default-root| - |default-root|> bjam **^** + |default-root|> b2 **^** More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^** More? **--build-type=complete** **msvc** stage Be sure to read `this note`__ about the appearance of ``^``, ``More?`` and quotation marks (``"``) in that line. -The option “\ **--build-type=complete**\ ” causes ``bjam`` to build +The option “\ **--build-type=complete**\ ” causes Boost.Build to build all supported variants of the libraries. For instructions on how to build only specific variants, please ask on the `Boost.Build mailing list`_. -- cgit v1.2.1