diff options
| author | Dave Abrahams <dave@boostpro.com> | 2007-04-28 01:35:31 +0000 |
|---|---|---|
| committer | Dave Abrahams <dave@boostpro.com> | 2007-04-28 01:35:31 +0000 |
| commit | d886d045a816a38c7b25862711f169466ad57cf0 (patch) | |
| tree | 8190a2df29c6f5446f3ebaee56f80c1b45949c63 | |
| parent | 0b038e7a8be471a56833d07433bea18ae2b66fb0 (diff) | |
| download | boost-d886d045a816a38c7b25862711f169466ad57cf0.tar.gz | |
Update link to Boost release
[SVN r37523]
| -rw-r--r-- | more/getting_started/detail/build-from-source-head.rst | 2 | ||||
| -rw-r--r-- | more/getting_started/detail/header-only.rst | 7 | ||||
| -rw-r--r-- | more/getting_started/detail/library-naming.rst | 6 | ||||
| -rw-r--r-- | more/getting_started/detail/release-variables.rst | 2 | ||||
| -rw-r--r-- | more/getting_started/index.html | 22 | ||||
| -rw-r--r-- | more/getting_started/unix-variants.html | 238 | ||||
| -rw-r--r-- | more/getting_started/unix-variants.rst | 2 | ||||
| -rw-r--r-- | more/getting_started/windows.html | 300 |
8 files changed, 295 insertions, 284 deletions
diff --git a/more/getting_started/detail/build-from-source-head.rst b/more/getting_started/detail/build-from-source-head.rst index 7e55da83b1..b2dfd5cad1 100644 --- a/more/getting_started/detail/build-from-source-head.rst +++ b/more/getting_started/detail/build-from-source-head.rst @@ -10,7 +10,7 @@ installing software. To use it, you'll need an executable called .. _precompiled-bjam: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941 -.. _Boost.Jam documentation: Boost.Jam_ +.. .. _Boost.Jam documentation: Boost.Jam_ .. _Boost.Build: ../../tools/build/index.html .. _Boost.Jam: ../../tools/jam/index.html .. _Boost.Build documentation: Boost.Build_ diff --git a/more/getting_started/detail/header-only.rst b/more/getting_started/detail/header-only.rst index 13d7e3fd7d..c1f1dd3b3e 100644 --- a/more/getting_started/detail/header-only.rst +++ b/more/getting_started/detail/header-only.rst @@ -15,20 +15,23 @@ Boost?” The good news is that often, there's nothing to build. require no separately-compiled library binaries or special treatment when linking. -.. _separate: +.. .. _separate: The only Boost libraries that *must* be built separately are: * Boost.Filesystem_ * Boost.IOStreams_ * Boost.ProgramOptions_ -* Boost.Python_ +* Boost.Python_ (see the `Boost.Python build documentation`__ + before building and installing it) * Boost.Regex_ * Boost.Serialization_ * Boost.Signals_ * Boost.Thread_ * Boost.Wave_ +__ ../../libs/python/doc/building.html + A few libraries have optional separately-compiled binaries: * Boost.DateTime_ has a binary component that is only needed if diff --git a/more/getting_started/detail/library-naming.rst b/more/getting_started/detail/library-naming.rst index ad1d512232..76d99ed5c2 100644 --- a/more/getting_started/detail/library-naming.rst +++ b/more/getting_started/detail/library-naming.rst @@ -19,7 +19,7 @@ following elements: *Library name*: all boost library filenames begin with ``boost_``. ``-vc71`` - *Toolset tag*: identifies the toolset and version used to build + *Toolset tag*: identifies the toolset_ and version used to build the binary. ``-mt`` @@ -68,13 +68,13 @@ following elements: ``.a`` and ``.so`` for static libraries (archives) and shared libraries, respectively. On Windows, ``.dll`` indicates a shared library and (except for static libraries built by the ``gcc`` - toolset, whose names always end in ``.a``) ``.lib`` indicates a + toolset_, whose names always end in ``.a``) ``.lib`` indicates a static or import library. Where supported by toolsets on unix variants, a full version extension is added (e.g. ".so.1.34") and a symbolic link to the library file, named without the trailing version number, will also be created. -.. _Boost.Build toolset names: toolset-name_ +.. .. _Boost.Build toolset names: toolset-name_ __ ../../libs/python/doc/building.html#variants diff --git a/more/getting_started/detail/release-variables.rst b/more/getting_started/detail/release-variables.rst index c8dc919531..1adbd3fb67 100644 --- a/more/getting_started/detail/release-variables.rst +++ b/more/getting_started/detail/release-variables.rst @@ -9,4 +9,4 @@ .. |boost_ver| replace:: ``boost_1_34_0`` .. |boost_ver-bold| replace:: **boost_1_34_0** -.. _sf-download: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=376197
\ No newline at end of file +.. _sf-download: http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041
\ No newline at end of file diff --git a/more/getting_started/index.html b/more/getting_started/index.html index c72e124216..2f60d00baa 100644 --- a/more/getting_started/index.html +++ b/more/getting_started/index.html @@ -9,19 +9,19 @@ </head> <body> <div class="document" id="logo-getting-started"> -<h1 class="title"><a class="reference" href="../../index.htm"><img alt="Boost" class="boost-logo" src="../../boost.png" /></a> Getting Started</h1> +<h1 class="title"><a class="reference external" href="../../index.htm"><img alt="Boost" class="boost-logo" src="../../boost.png" /></a> Getting Started</h1> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> -<div class="section"> -<h1><a id="welcome" name="welcome">Welcome</a></h1> +<div class="section" id="welcome"> +<h1>Welcome</h1> <p>Welcome to the Boost libraries! By the time you've completed this tutorial, you'll be at least somewhat comfortable with the contents of a Boost distribution and how to go about using it.</p> </div> -<div class="section"> -<h1><a id="what-s-here" name="what-s-here">What's Here</a></h1> +<div class="section" id="what-s-here"> +<h1>What's Here</h1> <p>This document is designed to be an <em>extremely</em> gentle introduction, so we included a fair amount of material that may already be very familiar to you. To keep things simple, we also left out some @@ -29,8 +29,8 @@ information intermediate and advanced users will probably want. At the end of this document, we'll refer you on to resources that can help you pursue these topics further.</p> </div> -<div class="section"> -<h1><a id="preliminaries" name="preliminaries">Preliminaries</a></h1> +<div class="section" id="preliminaries"> +<h1>Preliminaries</h1> <p>We use one typographic convention that might not be immediately obvious: <em>italic</em> text in examples is meant as a descriptive placeholder for something else, usually information that you'll @@ -41,16 +41,16 @@ provide. For example:</p> <p>Here you're expected to imagine replacing the text “your name” with your actual name.</p> </div> -<div class="section"> -<h1><a id="ready" name="ready">Ready?</a></h1> +<div class="section" id="ready"> +<h1>Ready?</h1> <p>Let's go!</p> </div> </div> <div class="footer"> <hr class="footer" /> <div class="nextpage line-block"> -<div class="line"><strong>Next:</strong> <a class="reference" href="windows.html">Getting Started on Microsoft Windows</a></div> -<div class="line"><strong>or:</strong> <a class="reference" href="unix-variants.html">Getting Started on Unix variants (e.g. Linux, MacOS)</a></div> +<div class="line"><strong>Next:</strong> <a class="reference external" href="windows.html">Getting Started on Microsoft Windows</a></div> +<div class="line"><strong>or:</strong> <a class="reference external" href="unix-variants.html">Getting Started on Unix variants (e.g. Linux, MacOS)</a></div> </div> </div> diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index 68c2ef0402..3e8f61bc69 100644 --- a/more/getting_started/unix-variants.html +++ b/more/getting_started/unix-variants.html @@ -10,7 +10,7 @@ </head> <body> <div class="document" id="logo-getting-started-on-unix-variants"> -<h1 class="title"><a class="reference" href="../../index.htm"><img alt="Boost" class="boost-logo" src="../../boost.png" /></a> Getting Started on Unix Variants</h1> +<h1 class="title"><a class="reference external" href="../../index.htm"><img alt="Boost" class="boost-logo" src="../../boost.png" /></a> Getting Started on Unix Variants</h1> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> @@ -27,43 +27,43 @@ .. _`Getting Started on Windows`: windows.html .. _Cygwin: http://www.cygwin.com .. _MinGW: http://mingw.org --> -<div class="contents topic"> -<p class="topic-title first"><a id="index" name="index">Index</a></p> +<div class="contents topic" id="index"> +<p class="topic-title first">Index</p> <ul class="auto-toc simple"> -<li><a class="reference" href="#get-boost" id="id17" name="id17">1 Get Boost</a></li> -<li><a class="reference" href="#the-boost-distribution" id="id18" name="id18">2 The Boost Distribution</a></li> -<li><a class="reference" href="#header-only-libraries" id="id19" name="id19">3 Header-Only Libraries</a></li> -<li><a class="reference" href="#build-a-simple-program-using-boost" id="id20" name="id20">4 Build a Simple Program Using Boost</a><ul class="auto-toc"> -<li><a class="reference" href="#errors-and-warnings" id="id21" name="id21">4.1 Errors and Warnings</a></li> +<li><a class="reference internal" href="#get-boost" id="id18">1 Get Boost</a></li> +<li><a class="reference internal" href="#the-boost-distribution" id="id19">2 The Boost Distribution</a></li> +<li><a class="reference internal" href="#header-only-libraries" id="id20">3 Header-Only Libraries</a></li> +<li><a class="reference internal" href="#build-a-simple-program-using-boost" id="id21">4 Build a Simple Program Using Boost</a><ul class="auto-toc"> +<li><a class="reference internal" href="#errors-and-warnings" id="id22">4.1 Errors and Warnings</a></li> </ul> </li> -<li><a class="reference" href="#prepare-to-use-a-boost-library-binary" id="id22" name="id22">5 Prepare to Use a Boost Library Binary</a><ul class="auto-toc"> -<li><a class="reference" href="#easy-build-and-install" id="id23" name="id23">5.1 Easy Build and Install</a></li> -<li><a class="reference" href="#or-custom-build-and-install" id="id24" name="id24">5.2 Or, Custom Build and Install</a><ul class="auto-toc"> -<li><a class="reference" href="#get-bjam" id="id25" name="id25">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> -<li><a class="reference" href="#identify-your-toolset" id="id26" name="id26">5.2.2 Identify Your Toolset</a></li> -<li><a class="reference" href="#select-a-build-directory" id="id27" name="id27">5.2.3 Select a Build Directory</a></li> -<li><a class="reference" href="#invoke-bjam" id="id28" name="id28">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> +<li><a class="reference internal" href="#prepare-to-use-a-boost-library-binary" id="id23">5 Prepare to Use a Boost Library Binary</a><ul class="auto-toc"> +<li><a class="reference internal" href="#easy-build-and-install" id="id24">5.1 Easy Build and Install</a></li> +<li><a class="reference internal" href="#or-custom-build-and-install" id="id25">5.2 Or, Custom Build and Install</a><ul class="auto-toc"> +<li><a class="reference internal" href="#get-bjam" id="id26">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> +<li><a class="reference internal" href="#identify-your-toolset" id="id27">5.2.2 Identify Your Toolset</a></li> +<li><a class="reference internal" href="#select-a-build-directory" id="id28">5.2.3 Select a Build Directory</a></li> +<li><a class="reference internal" href="#invoke-bjam" id="id29">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> </ul> </li> -<li><a class="reference" href="#expected-build-output" id="id29" name="id29">5.3 Expected Build Output</a></li> -<li><a class="reference" href="#in-case-of-build-errors" id="id30" name="id30">5.4 In Case of Build Errors</a></li> +<li><a class="reference internal" href="#expected-build-output" id="id30">5.3 Expected Build Output</a></li> +<li><a class="reference internal" href="#in-case-of-build-errors" id="id31">5.4 In Case of Build Errors</a></li> </ul> </li> -<li><a class="reference" href="#link-your-program-to-a-boost-library" id="id31" name="id31">6 Link Your Program to a Boost Library</a><ul class="auto-toc"> -<li><a class="reference" href="#library-naming" id="id32" name="id32">6.1 Library Naming</a></li> -<li><a class="reference" href="#test-your-program" id="id33" name="id33">6.2 Test Your Program</a></li> +<li><a class="reference internal" href="#link-your-program-to-a-boost-library" id="id32">6 Link Your Program to a Boost Library</a><ul class="auto-toc"> +<li><a class="reference internal" href="#library-naming" id="id33">6.1 Library Naming</a></li> +<li><a class="reference internal" href="#test-your-program" id="id34">6.2 Test Your Program</a></li> </ul> </li> -<li><a class="reference" href="#conclusion-and-further-resources" id="id34" name="id34">7 Conclusion and Further Resources</a></li> +<li><a class="reference internal" href="#conclusion-and-further-resources" id="id35">7 Conclusion and Further Resources</a></li> </ul> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id17" id="get-boost" name="get-boost">1 Get Boost</a></h1> +<div class="section" id="get-boost"> +<h1><a class="toc-backref" href="#id18">1 Get Boost</a></h1> <p>The most reliable way to get a copy of Boost is to download a -distribution from <a class="reference" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=376197">SourceForge</a>:</p> +distribution from <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041">SourceForge</a>:</p> <ol class="arabic"> -<li><p class="first">Download <tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">.tar.bz2</span></tt>.</p> +<li><p class="first">Download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">.tar.bz2</span></tt></a>.</p> </li> <li><p class="first">In the directory where you want to put the Boost installation, execute</p> @@ -79,16 +79,16 @@ library packages, however you may need to adapt these instructions if you use third-party packages, because their creators usually choose to break Boost up into several packages, reorganize the directory structure of the Boost distribution, -and/or rename the library binaries.<a class="footnote-reference" href="#packagers" id="id2" name="id2"><sup>1</sup></a> If you have +and/or rename the library binaries.<a class="footnote-reference" href="#packagers" id="id2"><sup>1</sup></a> If you have any trouble, we suggest using an official Boost distribution -from <a class="reference" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=376197">SourceForge</a>.</p> +from <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041">SourceForge</a>.</p> </div> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id18" id="the-boost-distribution" name="the-boost-distribution">2 The Boost Distribution</a></h1> +<div class="section" id="the-boost-distribution"> +<h1><a class="toc-backref" href="#id19">2 The Boost Distribution</a></h1> <p>This is a sketch of the resulting directory structure:</p> <pre class="literal-block"> <strong>boost_1_34_0</strong><strong>/</strong> .................<em>The “boost root directory”</em> @@ -123,7 +123,7 @@ the Python library's <tt class="docutils literal"><span class="pre">def.hpp</spa </li> <li><p class="first">Some libraries have an “aggregate header” in <tt class="docutils literal"><span class="pre">boost</span></tt><tt class="docutils literal"><span class="pre">/</span></tt> that <tt class="docutils literal"><span class="pre">#include</span></tt>s all of the library's other headers. For -example, <a class="reference" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p> +example, <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p> <pre class="literal-block"> <tt class="docutils literal"><span class="pre">boost</span></tt><tt class="docutils literal"><span class="pre">/</span></tt><tt class="docutils literal"><span class="pre">python.hpp</span></tt>. </pre> @@ -165,8 +165,8 @@ contains a subset of the Boost documentation. Start with <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id19" id="header-only-libraries" name="header-only-libraries">3 Header-Only Libraries</a></h1> +<div class="section" id="header-only-libraries"> +<h1><a class="toc-backref" href="#id20">3 Header-Only Libraries</a></h1> <p>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.</p> <div class="admonition-nothing-to-build admonition"> @@ -176,26 +176,28 @@ of header files</em> containing templates and inline functions, and require no separately-compiled library binaries or special treatment when linking.</p> </div> -<p id="separate">The only Boost libraries that <em>must</em> be built separately are:</p> +<!-- .. _separate: --> +<p>The only Boost libraries that <em>must</em> be built separately are:</p> <ul class="simple"> -<li><a class="reference" href="../../libs/filesystem/index.html">Boost.Filesystem</a></li> -<li><a class="reference" href="../../libs/iostreams/index.html">Boost.IOStreams</a></li> -<li><a class="reference" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li> -<li><a class="reference" href="../../libs/python/doc/building.html">Boost.Python</a></li> -<li><a class="reference" href="../../libs/regex/index.html">Boost.Regex</a></li> -<li><a class="reference" href="../../libs/serialization/index.html">Boost.Serialization</a></li> -<li><a class="reference" href="../../libs/signals/index.html">Boost.Signals</a></li> -<li><a class="reference" href="../../libs/thread/index.html">Boost.Thread</a></li> -<li><a class="reference" href="../../libs/wave/index.html">Boost.Wave</a></li> +<li><a class="reference external" href="../../libs/filesystem/index.html">Boost.Filesystem</a></li> +<li><a class="reference external" href="../../libs/iostreams/index.html">Boost.IOStreams</a></li> +<li><a class="reference external" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li> +<li><a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a> (see the <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python build documentation</a> +before building and installing it)</li> +<li><a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a></li> +<li><a class="reference external" href="../../libs/serialization/index.html">Boost.Serialization</a></li> +<li><a class="reference external" href="../../libs/signals/index.html">Boost.Signals</a></li> +<li><a class="reference external" href="../../doc/html/thread/build.html#thread.build">Boost.Thread</a></li> +<li><a class="reference external" href="../../libs/wave/index.html">Boost.Wave</a></li> </ul> <p>A few libraries have optional separately-compiled binaries:</p> <ul class="simple"> -<li><a class="reference" href="../../libs/date_time/index.html">Boost.DateTime</a> has a binary component that is only needed if +<li><a class="reference external" href="../../libs/date_time/index.html">Boost.DateTime</a> has a binary component that is only needed if you're using its <tt class="docutils literal"><span class="pre">to_string</span></tt>/<tt class="docutils literal"><span class="pre">from_string</span></tt> or serialization features, or if you're targeting Visual C++ 6.x or Borland.</li> -<li><a class="reference" href="../../libs/graph/index.html">Boost.Graph</a> also has a binary component that is only needed if -you intend to <a class="reference" href="../../libs/graph/doc/read_graphviz.html">parse GraphViz files</a>.</li> -<li><a class="reference" href="../../libs/test/index.html">Boost.Test</a> can be used in “header-only” or “separately compiled” +<li><a class="reference external" href="../../libs/graph/index.html">Boost.Graph</a> also has a binary component that is only needed if +you intend to <a class="reference external" href="../../libs/graph/doc/read_graphviz.html">parse GraphViz files</a>.</li> +<li><a class="reference external" href="../../libs/test/index.html">Boost.Test</a> can be used in “header-only” or “separately compiled” mode, although <strong>separate compilation is recommended for serious use</strong>.</li> </ul> @@ -203,8 +205,8 @@ use</strong>.</li> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id20" id="build-a-simple-program-using-boost" name="build-a-simple-program-using-boost">4 Build a Simple Program Using Boost</a></h1> +<div class="section" id="build-a-simple-program-using-boost"> +<h1><a class="toc-backref" href="#id21">4 Build a Simple Program Using Boost</a></h1> <p>To keep things simple, let's start by using a header-only library. The following program reads a sequence of integers from standard input, uses Boost.Lambda to multiply each number by three, and @@ -237,25 +239,25 @@ echo 1 2 3 | ./example <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> -<div class="section"> -<h2><a class="toc-backref" href="#id21" id="errors-and-warnings" name="errors-and-warnings">4.1 Errors and Warnings</a></h2> +<div class="section" id="errors-and-warnings"> +<h2><a class="toc-backref" href="#id22">4.1 Errors and Warnings</a></h2> <p>Don't be alarmed if you see compiler warnings originating in Boost headers. We try to eliminate them, but doing so isn't always -practical.<a class="footnote-reference" href="#warnings" id="id4" name="id4"><sup>3</sup></a> <strong>Errors are another matter</strong>. If you're +practical.<a class="footnote-reference" href="#warnings" id="id5"><sup>3</sup></a> <strong>Errors are another matter</strong>. If you're seeing compilation errors at this point in the tutorial, check to -be sure you've copied the <a class="reference" href="#build-a-simple-program-using-boost">example program</a> correctly and that you've -correctly identified the <a class="reference" href="#boost-root-directory">Boost root directory</a>.</p> +be sure you've copied the <a class="reference internal" href="#build-a-simple-program-using-boost">example program</a> correctly and that you've +correctly identified the <a class="reference internal" href="#boost-root-directory">Boost root directory</a>.</p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id22" id="prepare-to-use-a-boost-library-binary" name="prepare-to-use-a-boost-library-binary">5 Prepare to Use a Boost Library Binary</a></h1> +<div class="section" id="prepare-to-use-a-boost-library-binary"> +<h1><a class="toc-backref" href="#id23">5 Prepare to Use a Boost Library Binary</a></h1> <p>If you want to use any of the separately-compiled Boost libraries, you'll need to acquire library binaries.</p> -<div class="section"> -<h2><a class="toc-backref" href="#id23" id="easy-build-and-install" name="easy-build-and-install">5.1 Easy Build and Install</a></h2> +<div class="section" id="easy-build-and-install"> +<h2><a class="toc-backref" href="#id24">5.1 Easy Build and Install</a></h2> <p>Issue the following commands in the shell (don't type <tt class="docutils literal"><span class="pre">$</span></tt>; that represents the shell's prompt):</p> <pre class="literal-block"> @@ -280,34 +282,35 @@ installation prefix. You will also find a copy of the Boost headers in the <tt class="docutils literal"><span class="pre">include/</span></tt> subdirectory of the installation prefix, so you can henceforth use that directory as an <tt class="docutils literal"><span class="pre">#include</span></tt> path in place of the Boost root directory.</p> -<p><a class="reference" href="#link-your-program-to-a-boost-library"><em>skip to the next step</em></a></p> +<p><a class="reference internal" href="#link-your-program-to-a-boost-library"><em>skip to the next step</em></a></p> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id24" id="or-custom-build-and-install" name="or-custom-build-and-install">5.2 Or, Custom Build and Install</a></h2> +<div class="section" id="or-custom-build-and-install"> +<h2><a class="toc-backref" href="#id25">5.2 Or, Custom Build and Install</a></h2> <p>If you're using a compiler other than your system's default, you'll -need to use <a class="reference" href="../../tools/build/index.html">Boost.Build</a> to create binaries. You'll also +need to use <a class="reference external" href="../../tools/build/index.html">Boost.Build</a> to create binaries. You'll also use this method if you need a nonstandard build variant (see the -<a class="reference" href="../../tools/build/index.html">Boost.Build documentation</a> for more details).</p> +<a class="reference external" href="../../tools/build/index.html">Boost.Build documentation</a> for more details).</p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> -<p><a class="reference" href="../../tools/build/index.html">Boost.Build</a> is a text-based system for developing, testing, and +<p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> is a text-based system for developing, testing, and installing software. To use it, you'll need an executable called <tt class="docutils literal"><span class="pre">bjam</span></tt>.</p> -<div class="section"> -<h3><a class="toc-backref" href="#id25" id="get-bjam" name="get-bjam">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> +<!-- .. _Boost.Jam documentation: Boost.Jam_ --> +<div class="section" id="get-bjam"> +<h3><a class="toc-backref" href="#id26">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> <p><tt class="docutils literal"><span class="pre">bjam</span></tt> is the command-line tool that drives the Boost Build system. To build Boost binaries, you'll invoke <tt class="docutils literal"><span class="pre">bjam</span></tt> from the Boost root.</p> -<p>Boost provides <a class="reference" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941">pre-compiled <tt class="docutils literal"><span class="pre">bjam</span></tt> executables</a> for a variety of platforms. -Alternatively, you can build <tt class="docutils literal"><span class="pre">bjam</span></tt> yourself using <a class="reference" href="../../doc/html/jam/building.html">these +<p>Boost provides <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941">pre-compiled <tt class="docutils literal"><span class="pre">bjam</span></tt> executables</a> for a variety of platforms. +Alternatively, you can build <tt class="docutils literal"><span class="pre">bjam</span></tt> yourself using <a class="reference external" href="../../doc/html/jam/building.html">these instructions</a>.</p> </div> -<div class="section"> -<h3><a class="toc-backref" href="#id26" id="identify-your-toolset" name="identify-your-toolset"><span id="toolset-name"></span><span id="toolset"></span>5.2.2 Identify Your Toolset</a></h3> +<div class="section" id="identify-your-toolset"> +<span id="toolset-name"></span><span id="toolset"></span><h3><a class="toc-backref" href="#id27">5.2.2 Identify Your Toolset</a></h3> <p>First, find the toolset corresponding to your compiler in the following table.</p> -<table border="1" class="docutils table"> +<table border="1" class="docutils"> <colgroup> <col width="18%" /> <col width="33%" /> @@ -333,7 +336,7 @@ known to work well with Boost</td> <tr><td><tt class="docutils literal"><span class="pre">como</span></tt></td> <td>Comeau Computing</td> <td>Using this toolset may -require <a class="reference" href="../../tools/build/index.html">configuring</a> another +require <a class="reference external" href="../../tools/build/index.html">configuring</a> another toolset to act as its backend</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">cw</span></tt></td> @@ -405,20 +408,20 @@ affect this step in any way; you still need to select a Boost.Build toolset from the table.</p> </div> </div> -<div class="section"> -<h3><a class="toc-backref" href="#id27" id="select-a-build-directory" name="select-a-build-directory"><span id="id9"></span><span id="build-directory"></span>5.2.3 Select a Build Directory</a></h3> -<p><a class="reference" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while +<div class="section" id="select-a-build-directory"> +<span id="id10"></span><span id="build-directory"></span><h3><a class="toc-backref" href="#id28">5.2.3 Select a Build Directory</a></h3> +<p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while building into the <strong>build directory</strong>. If your Boost root directory is writable, this step isn't strictly necessary: by default Boost.Build will create a <tt class="docutils literal"><span class="pre">bin.v2/</span></tt> subdirectory for that purpose in your current working directory.</p> </div> -<div class="section"> -<h3><a class="toc-backref" href="#id28" id="invoke-bjam" name="invoke-bjam">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> +<div class="section" id="invoke-bjam"> +<h3><a class="toc-backref" href="#id29">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> <p>Change your current directory to the Boost root directory and invoke <tt class="docutils literal"><span class="pre">bjam</span></tt> as follows:</p> <pre class="literal-block"> -bjam <strong>--build-dir=</strong><a class="reference" href="#id9"><em>build-directory</em></a> <strong>--toolset=</strong><a class="reference" href="#toolset-name"><em>toolset-name</em></a> stage +bjam <strong>--build-dir=</strong><a class="reference internal" href="#id10"><em>build-directory</em></a> <strong>--toolset=</strong><a class="reference internal" href="#toolset-name"><em>toolset-name</em></a> stage </pre> <p>For example, your session might look like this:</p> <pre class="literal-block"> @@ -429,7 +432,7 @@ $ bjam <strong>--build-dir=</strong>/tmp/build-boost <strong>--toolset=</strong> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> <p>Boost.Build will place the Boost binaries in the <tt class="docutils literal"><span class="pre">stage</span></tt><tt class="docutils literal"><span class="pre">/</span></tt> -subdirectory of your <a class="reference" href="#build-directory">build directory</a>.</p> +subdirectory of your <a class="reference internal" href="#build-directory">build directory</a>.</p> <div class="note"> <p class="first admonition-title">Note</p> <p class="last"><tt class="docutils literal"><span class="pre">bjam</span></tt> is case-sensitive; it is important that all the @@ -450,8 +453,8 @@ be interested in:</p> </ul> </div> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id29" id="expected-build-output" name="expected-build-output">5.3 Expected Build Output</a></h2> +<div class="section" id="expected-build-output"> +<h2><a class="toc-backref" href="#id30">5.3 Expected Build Output</a></h2> <p>During the process of building Boost libraries, you can expect to see some messages printed on the console. These may include</p> <ul> @@ -474,29 +477,29 @@ look something like:</p> </li> </ul> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id30" id="in-case-of-build-errors" name="in-case-of-build-errors">5.4 In Case of Build Errors</a></h2> +<div class="section" id="in-case-of-build-errors"> +<h2><a class="toc-backref" href="#id31">5.4 In Case of Build Errors</a></h2> <p>The only error messages you see when building Boost—if any—should be related to the IOStreams library's support of zip and bzip2 -formats as described <a class="reference" href="../../libs/iostreams/doc/installation.html">here</a>. Install the relevant development +formats as described <a class="reference external" href="../../libs/iostreams/doc/installation.html">here</a>. Install the relevant development packages for libz and libbz2 if you need those features. Other errors when building Boost libraries are cause for concern.</p> <p>If it seems like the build system can't find your compiler and/or linker, consider setting up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file as described -in the <a class="reference" href="../../tools/build/index.html">Boost.Build documentation</a>. If that isn't your problem or +in the <a class="reference external" href="../../tools/build/index.html">Boost.Build documentation</a>. If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file doesn't work for you, please address questions about configuring Boost for your compiler to the -<a class="reference" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p> +<a class="reference external" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id31" id="link-your-program-to-a-boost-library" name="link-your-program-to-a-boost-library">6 Link Your Program to a Boost Library</a></h1> +<div class="section" id="link-your-program-to-a-boost-library"> +<h1><a class="toc-backref" href="#id32">6 Link Your Program to a Boost Library</a></h1> <p>To demonstrate linking with a Boost binary library, we'll use the following simple program that extracts the subject lines from -emails. It uses the <a class="reference" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a +emails. It uses the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a separately-compiled binary component.</p> <pre class="literal-block"> #include <boost/regex.hpp> @@ -533,7 +536,7 @@ $ c++ -I <em>path/to/</em><tt class="docutils literal"><span class="pre">boost_1 <strong>~/boost/lib/libboost_regex-gcc-3.4-mt-d-1_34.a</strong> </pre> </li> -<li><p class="first">You can separately specify a directory to search (with <tt class="docutils literal"><span class="pre">-L</span></tt><em>directory</em>) and a library name to search for (with <tt class="docutils literal"><span class="pre">-l</span></tt><em>library</em>,<a class="footnote-reference" href="#lowercase-l" id="id11" name="id11"><sup>2</sup></a> dropping the filename's leading <tt class="docutils literal"><span class="pre">lib</span></tt> and trailing +<li><p class="first">You can separately specify a directory to search (with <tt class="docutils literal"><span class="pre">-L</span></tt><em>directory</em>) and a library name to search for (with <tt class="docutils literal"><span class="pre">-l</span></tt><em>library</em>,<a class="footnote-reference" href="#lowercase-l" id="id12"><sup>2</sup></a> dropping the filename's leading <tt class="docutils literal"><span class="pre">lib</span></tt> and trailing suffix (<tt class="docutils literal"><span class="pre">.a</span></tt> in this case):</p> <pre class="literal-block"> $ c++ -I <em>path/to/</em><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt> example.cpp -o example <strong>\</strong> @@ -548,10 +551,10 @@ automatically for you unless you pass a special option such as <tt class="docutils literal"><span class="pre">-static</span></tt> on the command line.</p> </li> </ol> -<p>In both cases above, the bold text is what you'd add to <a class="reference" href="#build-a-simple-program-using-boost">the +<p>In both cases above, the bold text is what you'd add to <a class="reference internal" href="#build-a-simple-program-using-boost">the command lines we explored earlier</a>.</p> -<div class="section"> -<h2><a class="toc-backref" href="#id32" id="library-naming" name="library-naming">6.1 Library Naming</a></h2> +<div class="section" id="library-naming"> +<h2><a class="toc-backref" href="#id33">6.1 Library Naming</a></h2> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> @@ -566,11 +569,11 @@ following elements:</p> <dd><em>Prefix</em>: except on Microsoft Windows, every Boost library name begins with this string. On Windows, only ordinary static libraries use the <tt class="docutils literal"><span class="pre">lib</span></tt> prefix; import libraries and DLLs do -not.<a class="footnote-reference" href="#distinct" id="id13" name="id13"><sup>4</sup></a></dd> +not.<a class="footnote-reference" href="#distinct" id="id14"><sup>4</sup></a></dd> <dt><tt class="docutils literal"><span class="pre">boost_regex</span></tt></dt> <dd><em>Library name</em>: all boost library filenames begin with <tt class="docutils literal"><span class="pre">boost_</span></tt>.</dd> <dt><tt class="docutils literal"><span class="pre">-vc71</span></tt></dt> -<dd><em>Toolset tag</em>: identifies the toolset and version used to build +<dd><em>Toolset tag</em>: identifies the <a class="reference internal" href="#toolset">toolset</a> and version used to build the binary.</dd> <dt><tt class="docutils literal"><span class="pre">-mt</span></tt></dt> <dd><em>Threading tag</em>: indicates that the library was @@ -582,7 +585,7 @@ of <tt class="docutils literal"><span class="pre">-mt</span></tt>.</dd> interoperability with other compiled code. For each such feature, a single letter is added to the tag:</p> <blockquote> -<table border="1" class="docutils table"> +<table border="1" class="docutils"> <colgroup> <col width="6%" /> <col width="94%" /> @@ -601,17 +604,17 @@ libraries.</td> <td>using debug versions of the standard and runtime support libraries.</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">y</span></tt></td> -<td>using a special <a class="reference" href="../../libs/python/doc/building.html#variants">debug build of Python</a>.</td> +<td>using a special <a class="reference external" href="../../libs/python/doc/building.html#variants">debug build of Python</a>.</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">d</span></tt></td> -<td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id14" name="id14"><sup>5</sup></a></td> +<td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id15"><sup>5</sup></a></td> </tr> <tr><td><tt class="docutils literal"><span class="pre">p</span></tt></td> <td>using the STLPort standard library rather than the default one supplied with your compiler.</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">n</span></tt></td> -<td>using STLPort's deprecated “native iostreams” feature.<a class="footnote-reference" href="#native" id="id15" name="id15"><sup>6</sup></a></td> +<td>using STLPort's deprecated “native iostreams” feature.<a class="footnote-reference" href="#native" id="id16"><sup>6</sup></a></td> </tr> </tbody> </table> @@ -632,18 +635,19 @@ convention. On most unix-style platforms the extensions are <tt class="docutils literal"><span class="pre">.a</span></tt> and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared libraries, respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared library and (except for static libraries built by the <tt class="docutils literal"><span class="pre">gcc</span></tt> -toolset, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a +<a class="reference internal" href="#toolset">toolset</a>, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a static or import library. Where supported by toolsets on unix variants, a full version extension is added (e.g. ".so.1.34") and a symbolic link to the library file, named without the trailing version number, will also be created.</dd> </dl> +<!-- .. _Boost.Build toolset names: toolset-name_ --> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id33" id="test-your-program" name="test-your-program">6.2 Test Your Program</a></h2> +<div class="section" id="test-your-program"> +<h2><a class="toc-backref" href="#id34">6.2 Test Your Program</a></h2> <p>To test our subject extraction, we'll filter the following text file. Copy it out of your browser and save it as <tt class="docutils literal"><span class="pre">jayne.txt</span></tt>:</p> <pre class="literal-block"> @@ -682,23 +686,23 @@ Spoil Rock Hunter?”</p> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id34" id="conclusion-and-further-resources" name="conclusion-and-further-resources">7 Conclusion and Further Resources</a></h1> +<div class="section" id="conclusion-and-further-resources"> +<h1><a class="toc-backref" href="#id35">7 Conclusion and Further Resources</a></h1> <p>This concludes your introduction to Boost and to integrating it with your programs. As you start using Boost in earnest, there are surely a few additional points you'll wish we had covered. One day we may have a “Book 2 in the Getting Started series” that addresses them. Until then, we suggest you pursue the following resources. If you can't find what you need, or there's anything we can do to -make this document clearer, please post it to the <a class="reference" href="../../more/mailing_lists.htm#users">Boost Users' +make this document clearer, please post it to the <a class="reference external" href="../../more/mailing_lists.htm#users">Boost Users' mailing list</a>.</p> <ul class="simple"> -<li><a class="reference" href="../../tools/build/v2">Boost.Build reference manual</a></li> -<li><a class="reference" href="../../tools/jam/index.html">Boost.Jam reference manual</a></li> -<li><a class="reference" href="../../more/mailing_lists.htm#users">Boost Users' mailing list</a></li> -<li><a class="reference" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li> -<li><a class="reference" href="http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V2">Boost.Build Wiki</a></li> -<li><a class="reference" href="../../libs/index.html">Index of all Boost library documentation</a></li> +<li><a class="reference external" href="../../tools/build/v2">Boost.Build reference manual</a></li> +<li><a class="reference external" href="../../tools/jam/index.html">Boost.Jam reference manual</a></li> +<li><a class="reference external" href="../../more/mailing_lists.htm#users">Boost Users' mailing list</a></li> +<li><a class="reference external" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li> +<li><a class="reference external" href="http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V2">Boost.Build Wiki</a></li> +<li><a class="reference external" href="../../libs/index.html">Index of all Boost library documentation</a></li> </ul> <div class="admonition-onward admonition"> <p class="first admonition-title">Onward</p> @@ -711,17 +715,17 @@ mailing list</a>.</p> <table class="docutils footnote" frame="void" id="packagers" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id2" name="packagers">[1]</a></td><td><p class="first">If developers of Boost packages would like to work +<tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td><p class="first">If developers of Boost packages would like to work with us to make sure these instructions can be used with their packages, we'd be glad to help. Please make your interest known -to the <a class="reference" href="../../more/mailing_lists.htm#main">Boost developers' list</a>.</p> +to the <a class="reference external" href="../../more/mailing_lists.htm#main">Boost developers' list</a>.</p> </td></tr> </tbody> </table> <table class="docutils footnote" frame="void" id="lowercase-l" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id11" name="lowercase-l">[2]</a></td><td>That option is a dash followed by a lowercase “L” +<tr><td class="label"><a class="fn-backref" href="#id12">[2]</a></td><td>That option is a dash followed by a lowercase “L” character, which looks very much like a numeral 1 in some fonts.</td></tr> </tbody> </table> @@ -731,7 +735,7 @@ character, which looks very much like a numeral 1 in some fonts.</td></tr> <table class="docutils footnote" frame="void" id="warnings" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id4" name="warnings">[3]</a></td><td>Remember that warnings are specific to each compiler +<tr><td class="label"><a class="fn-backref" href="#id5">[3]</a></td><td>Remember that warnings are specific to each compiler implementation. The developer of a given Boost library might not have access to your compiler. Also, some warnings are extremely difficult to eliminate in generic code, to the point @@ -742,7 +746,7 @@ have any source code mechanism for suppressing warnings.</td></tr> <table class="docutils footnote" frame="void" id="distinct" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id13" name="distinct">[4]</a></td><td>This convention distinguishes the static version of +<tr><td class="label"><a class="fn-backref" href="#id14">[4]</a></td><td>This convention distinguishes the static version of a Boost library from the import library for an identically-configured Boost DLL, which would otherwise have the same name.</td></tr> @@ -751,7 +755,7 @@ same name.</td></tr> <table class="docutils footnote" frame="void" id="debug-abi" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id14" name="debug-abi">[5]</a></td><td>These libraries were compiled without optimization +<tr><td class="label"><a class="fn-backref" href="#id15">[5]</a></td><td>These libraries were compiled without optimization or inlining, with full debug symbols enabled, and without <tt class="docutils literal"><span class="pre">NDEBUG</span></tt> <tt class="docutils literal"><span class="pre">#define</span></tt>d. Although it's true that sometimes these choices don't affect binary compatibility with other @@ -761,7 +765,7 @@ compiled code, you can't count on that with Boost libraries.</td></tr> <table class="docutils footnote" frame="void" id="native" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id15" name="native">[6]</a></td><td>This feature of STLPort is deprecated because it's +<tr><td class="label"><a class="fn-backref" href="#id16">[6]</a></td><td>This feature of STLPort is deprecated because it's impossible to make it work transparently to the user; we don't recommend it.</td></tr> </tbody> diff --git a/more/getting_started/unix-variants.rst b/more/getting_started/unix-variants.rst index 6924468c96..fe39dba943 100644 --- a/more/getting_started/unix-variants.rst +++ b/more/getting_started/unix-variants.rst @@ -40,7 +40,7 @@ distribution from SourceForge_: .. _SourceForge: `sf-download`_ -1. Download |boost.tar.bz2|. +1. Download |boost.tar.bz2|_. 2. In the directory where you want to put the Boost installation, execute diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html index dbf529ee30..9d2a8d56fc 100644 --- a/more/getting_started/windows.html +++ b/more/getting_started/windows.html @@ -9,74 +9,74 @@ </head> <body> <div class="document" id="logo-getting-started-on-windows"> -<h1 class="title"><a class="reference" href="../../index.htm"><img alt="Boost" class="boost-logo" src="../../boost.png" /></a> Getting Started on Windows</h1> +<h1 class="title"><a class="reference external" href="../../index.htm"><img alt="Boost" class="boost-logo" src="../../boost.png" /></a> Getting Started on Windows</h1> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> <div class="admonition-a-note-to-cygwin-and-mingw-users admonition"> -<p class="first admonition-title">A note to <a class="reference" href="http://www.cygwin.com">Cygwin</a> and <a class="reference" href="http://mingw.org">MinGW</a> users</p> +<p class="first admonition-title">A note to <a class="reference external" href="http://www.cygwin.com">Cygwin</a> and <a class="reference external" href="http://mingw.org">MinGW</a> users</p> <p class="last">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 <a class="reference" href="http://www.cygwin.com">Cygwin</a> +you're in the right place. If you plan to build from the <a class="reference external" href="http://www.cygwin.com">Cygwin</a> bash shell, you're actually running on a POSIX platform and -should follow the instructions for <a class="reference" href="unix-variants.html">getting started on Unix -variants</a>. Other command shells, such as <a class="reference" href="http://mingw.org">MinGW</a>'s MSYS, are +should follow the instructions for <a class="reference external" href="unix-variants.html">getting started on Unix +variants</a>. Other command shells, such as <a class="reference external" href="http://mingw.org">MinGW</a>'s MSYS, are not supported—they may or may not work.</p> </div> -<div class="contents topic"> -<p class="topic-title first"><a id="index" name="index">Index</a></p> +<div class="contents topic" id="index"> +<p class="topic-title first">Index</p> <ul class="auto-toc simple"> -<li><a class="reference" href="#get-boost" id="id21" name="id21">1 Get Boost</a></li> -<li><a class="reference" href="#the-boost-distribution" id="id22" name="id22">2 The Boost Distribution</a></li> -<li><a class="reference" href="#header-only-libraries" id="id23" name="id23">3 Header-Only Libraries</a></li> -<li><a class="reference" href="#build-a-simple-program-using-boost" id="id24" name="id24">4 Build a Simple Program Using Boost</a><ul class="auto-toc"> -<li><a class="reference" href="#build-from-the-visual-studio-ide" id="id25" name="id25">4.1 Build From the Visual Studio IDE</a></li> -<li><a class="reference" href="#or-build-from-the-command-prompt" id="id26" name="id26">4.2 Or, Build From the Command Prompt</a></li> -<li><a class="reference" href="#errors-and-warnings" id="id27" name="id27">4.3 Errors and Warnings</a></li> +<li><a class="reference internal" href="#get-boost" id="id22">1 Get Boost</a></li> +<li><a class="reference internal" href="#the-boost-distribution" id="id23">2 The Boost Distribution</a></li> +<li><a class="reference internal" href="#header-only-libraries" id="id24">3 Header-Only Libraries</a></li> +<li><a class="reference internal" href="#build-a-simple-program-using-boost" id="id25">4 Build a Simple Program Using Boost</a><ul class="auto-toc"> +<li><a class="reference internal" href="#build-from-the-visual-studio-ide" id="id26">4.1 Build From the Visual Studio IDE</a></li> +<li><a class="reference internal" href="#or-build-from-the-command-prompt" id="id27">4.2 Or, Build From the Command Prompt</a></li> +<li><a class="reference internal" href="#errors-and-warnings" id="id28">4.3 Errors and Warnings</a></li> </ul> </li> -<li><a class="reference" href="#prepare-to-use-a-boost-library-binary" id="id28" name="id28">5 Prepare to Use a Boost Library Binary</a><ul class="auto-toc"> -<li><a class="reference" href="#install-visual-studio-2005-or-net-2003-binaries" id="id29" name="id29">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></li> -<li><a class="reference" href="#or-build-and-install-binaries-from-source" id="id30" name="id30">5.2 Or, Build and Install Binaries From Source</a><ul class="auto-toc"> -<li><a class="reference" href="#get-bjam" id="id31" name="id31">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> -<li><a class="reference" href="#identify-your-toolset" id="id32" name="id32">5.2.2 Identify Your Toolset</a></li> -<li><a class="reference" href="#select-a-build-directory" id="id33" name="id33">5.2.3 Select a Build Directory</a></li> -<li><a class="reference" href="#invoke-bjam" id="id34" name="id34">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> +<li><a class="reference internal" href="#prepare-to-use-a-boost-library-binary" id="id29">5 Prepare to Use a Boost Library Binary</a><ul class="auto-toc"> +<li><a class="reference internal" href="#install-visual-studio-2005-or-net-2003-binaries" id="id30">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></li> +<li><a class="reference internal" href="#or-build-and-install-binaries-from-source" id="id31">5.2 Or, Build and Install Binaries From Source</a><ul class="auto-toc"> +<li><a class="reference internal" href="#get-bjam" id="id32">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> +<li><a class="reference internal" href="#identify-your-toolset" id="id33">5.2.2 Identify Your Toolset</a></li> +<li><a class="reference internal" href="#select-a-build-directory" id="id34">5.2.3 Select a Build Directory</a></li> +<li><a class="reference internal" href="#invoke-bjam" id="id35">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li> </ul> </li> -<li><a class="reference" href="#expected-build-output" id="id35" name="id35">5.3 Expected Build Output</a></li> -<li><a class="reference" href="#in-case-of-build-errors" id="id36" name="id36">5.4 In Case of Build Errors</a></li> +<li><a class="reference internal" href="#expected-build-output" id="id36">5.3 Expected Build Output</a></li> +<li><a class="reference internal" href="#in-case-of-build-errors" id="id37">5.4 In Case of Build Errors</a></li> </ul> </li> -<li><a class="reference" href="#link-your-program-to-a-boost-library" id="id37" name="id37">6 Link Your Program to a Boost Library</a><ul class="auto-toc"> -<li><a class="reference" href="#link-from-within-the-visual-studio-ide" id="id38" name="id38">6.1 Link From Within the Visual Studio IDE</a></li> -<li><a class="reference" href="#or-link-from-the-command-prompt" id="id39" name="id39">6.2 Or, Link From the Command Prompt</a></li> -<li><a class="reference" href="#library-naming" id="id40" name="id40">6.3 Library Naming</a></li> -<li><a class="reference" href="#test-your-program" id="id41" name="id41">6.4 Test Your Program</a></li> +<li><a class="reference internal" href="#link-your-program-to-a-boost-library" id="id38">6 Link Your Program to a Boost Library</a><ul class="auto-toc"> +<li><a class="reference internal" href="#link-from-within-the-visual-studio-ide" id="id39">6.1 Link From Within the Visual Studio IDE</a></li> +<li><a class="reference internal" href="#or-link-from-the-command-prompt" id="id40">6.2 Or, Link From the Command Prompt</a></li> +<li><a class="reference internal" href="#library-naming" id="id41">6.3 Library Naming</a></li> +<li><a class="reference internal" href="#test-your-program" id="id42">6.4 Test Your Program</a></li> </ul> </li> -<li><a class="reference" href="#conclusion-and-further-resources" id="id42" name="id42">7 Conclusion and Further Resources</a></li> +<li><a class="reference internal" href="#conclusion-and-further-resources" id="id43">7 Conclusion and Further Resources</a></li> </ul> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id21" id="get-boost" name="get-boost">1 Get Boost</a></h1> -<p>The easiest way to get a copy of Boost is to use the <a class="reference" href="http://www.boost-consulting.com/download/windows">installer</a> -provided by <a class="reference" href="http://www.boost-consulting.com">Boost Consulting</a>. We especially recommend this +<div class="section" id="get-boost"> +<h1><a class="toc-backref" href="#id22">1 Get Boost</a></h1> +<p>The easiest way to get a copy of Boost is to use the <a class="reference external" href="http://www.boost-consulting.com/download/windows">installer</a> +provided by <a class="reference external" href="http://www.boost-consulting.com">Boost Consulting</a>. We especially recommend this method if you use Microsoft Visual Studio .NET 2003 or Microsoft Visual Studio 2005, because the installer can download and install precompiled library binaries, saving you the trouble of building them yourself. To complete this tutorial, you'll need to at least -install the <a class="reference" href="../../libs/regex/index.html">Boost.Regex</a> binaries when given the option.</p> +install the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> binaries when given the option.</p> <p>If you're using an earlier version of Visual Studio or some other compiler, or if you prefer to build everything yourself, you can -download <a class="reference" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=376197"><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">.exe</span></tt></a> and run it to install a complete Boost -distribution.<a class="footnote-reference" href="#zip" id="id2" name="id2"><sup>1</sup></a></p> +download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">.exe</span></tt></a> and run it to install a complete Boost +distribution.<a class="footnote-reference" href="#zip" id="id2"><sup>1</sup></a></p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id22" id="the-boost-distribution" name="the-boost-distribution">2 The Boost Distribution</a></h1> +<div class="section" id="the-boost-distribution"> +<h1><a class="toc-backref" href="#id23">2 The Boost Distribution</a></h1> <p>This is a sketch of the resulting directory structure:</p> <pre class="literal-block"> <strong>boost_1_34_0</strong><strong>\</strong> .................<em>The “boost root directory”</em> @@ -111,7 +111,7 @@ the Python library's <tt class="docutils literal"><span class="pre">def.hpp</spa </li> <li><p class="first">Some libraries have an “aggregate header” in <tt class="docutils literal"><span class="pre">boost</span></tt><tt class="docutils literal"><span class="pre">\</span></tt> that <tt class="docutils literal"><span class="pre">#include</span></tt>s all of the library's other headers. For -example, <a class="reference" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p> +example, <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p> <pre class="literal-block"> <tt class="docutils literal"><span class="pre">boost</span></tt><tt class="docutils literal"><span class="pre">\</span></tt><tt class="docutils literal"><span class="pre">python.hpp</span></tt>. </pre> @@ -158,8 +158,8 @@ contains a subset of the Boost documentation. Start with <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id23" id="header-only-libraries" name="header-only-libraries">3 Header-Only Libraries</a></h1> +<div class="section" id="header-only-libraries"> +<h1><a class="toc-backref" href="#id24">3 Header-Only Libraries</a></h1> <p>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.</p> <div class="admonition-nothing-to-build admonition"> @@ -169,26 +169,28 @@ of header files</em> containing templates and inline functions, and require no separately-compiled library binaries or special treatment when linking.</p> </div> -<p id="separate">The only Boost libraries that <em>must</em> be built separately are:</p> +<!-- .. _separate: --> +<p>The only Boost libraries that <em>must</em> be built separately are:</p> <ul class="simple"> -<li><a class="reference" href="../../libs/filesystem/index.html">Boost.Filesystem</a></li> -<li><a class="reference" href="../../libs/iostreams/index.html">Boost.IOStreams</a></li> -<li><a class="reference" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li> -<li><a class="reference" href="../../libs/python/doc/building.html">Boost.Python</a></li> -<li><a class="reference" href="../../libs/regex/index.html">Boost.Regex</a></li> -<li><a class="reference" href="../../libs/serialization/index.html">Boost.Serialization</a></li> -<li><a class="reference" href="../../libs/signals/index.html">Boost.Signals</a></li> -<li><a class="reference" href="../../libs/thread/index.html">Boost.Thread</a></li> -<li><a class="reference" href="../../libs/wave/index.html">Boost.Wave</a></li> +<li><a class="reference external" href="../../libs/filesystem/index.html">Boost.Filesystem</a></li> +<li><a class="reference external" href="../../libs/iostreams/index.html">Boost.IOStreams</a></li> +<li><a class="reference external" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li> +<li><a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a> (see the <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python build documentation</a> +before building and installing it)</li> +<li><a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a></li> +<li><a class="reference external" href="../../libs/serialization/index.html">Boost.Serialization</a></li> +<li><a class="reference external" href="../../libs/signals/index.html">Boost.Signals</a></li> +<li><a class="reference external" href="../../doc/html/thread/build.html#thread.build">Boost.Thread</a></li> +<li><a class="reference external" href="../../libs/wave/index.html">Boost.Wave</a></li> </ul> <p>A few libraries have optional separately-compiled binaries:</p> <ul class="simple"> -<li><a class="reference" href="../../libs/date_time/index.html">Boost.DateTime</a> has a binary component that is only needed if +<li><a class="reference external" href="../../libs/date_time/index.html">Boost.DateTime</a> has a binary component that is only needed if you're using its <tt class="docutils literal"><span class="pre">to_string</span></tt>/<tt class="docutils literal"><span class="pre">from_string</span></tt> or serialization features, or if you're targeting Visual C++ 6.x or Borland.</li> -<li><a class="reference" href="../../libs/graph/index.html">Boost.Graph</a> also has a binary component that is only needed if -you intend to <a class="reference" href="../../libs/graph/doc/read_graphviz.html">parse GraphViz files</a>.</li> -<li><a class="reference" href="../../libs/test/index.html">Boost.Test</a> can be used in “header-only” or “separately compiled” +<li><a class="reference external" href="../../libs/graph/index.html">Boost.Graph</a> also has a binary component that is only needed if +you intend to <a class="reference external" href="../../libs/graph/doc/read_graphviz.html">parse GraphViz files</a>.</li> +<li><a class="reference external" href="../../libs/test/index.html">Boost.Test</a> can be used in “header-only” or “separately compiled” mode, although <strong>separate compilation is recommended for serious use</strong>.</li> </ul> @@ -196,8 +198,8 @@ use</strong>.</li> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id24" id="build-a-simple-program-using-boost" name="build-a-simple-program-using-boost">4 Build a Simple Program Using Boost</a></h1> +<div class="section" id="build-a-simple-program-using-boost"> +<h1><a class="toc-backref" href="#id25">4 Build a Simple Program Using Boost</a></h1> <p>To keep things simple, let's start by using a header-only library. The following program reads a sequence of integers from standard input, uses Boost.Lambda to multiply each number by three, and @@ -218,11 +220,11 @@ int main() } </pre> <p>Copy the text of this program into a file called <tt class="docutils literal"><span class="pre">example.cpp</span></tt>.</p> -<div class="note"> -<p class="first admonition-title"><a id="command-line-tool" name="command-line-tool"><span id="command-prompt"></span>Note</a></p> +<div class="note" id="command-line-tool"> +<span id="command-prompt"></span><p class="first admonition-title">Note</p> <p class="last">To build the examples in this guide, you can use an Integrated Development Environment (IDE) like Visual Studio, or -you can issue commands from the <a class="reference" href="#command-prompt">command prompt</a>. Since every +you can issue commands from the <a class="reference internal" href="#command-prompt">command prompt</a>. Since every IDE and compiler has different options and Microsoft's are by far the dominant compilers on Windows, we only give specific directions here for Visual Studio 2005 and .NET 2003 IDEs and @@ -252,8 +254,8 @@ cd <tt class="docutils literal"><span class="pre">C:\Program</span> <span class= caret (<tt class="docutils literal"><span class="pre">^</span></tt>) at the end of all but the last line. Some examples on this page use that technique to save horizontal space.</p> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id25" id="build-from-the-visual-studio-ide" name="build-from-the-visual-studio-ide"><span id="vs-header-only"></span>4.1 Build From the Visual Studio IDE</a></h2> +<div class="section" id="build-from-the-visual-studio-ide"> +<span id="vs-header-only"></span><h2><a class="toc-backref" href="#id26">4.1 Build From the Visual Studio IDE</a></h2> <ul> <li><p class="first">From Visual Studio's <em>File</em> menu, select <em>New</em> > <em>Project…</em></p> </li> @@ -276,7 +278,7 @@ Directories</em>, enter the path to the Boost root directory, for example</p> </li> <li><p class="first">In <em>Configuration Properties</em> > <em>C/C++</em> > <em>Precompiled Headers</em>, change <em>Use Precompiled Header (/Yu)</em> to <em>Not Using Precompiled -Headers</em>.<a class="footnote-reference" href="#pch" id="id4" name="id4"><sup>3</sup></a></p> +Headers</em>.<a class="footnote-reference" href="#pch" id="id5"><sup>3</sup></a></p> </li> <li><p class="first">Replace the contents of the <tt class="docutils literal"><span class="pre">example.cpp</span></tt> generated by the IDE with the example code above.</p> @@ -291,10 +293,10 @@ into the resulting window, followed by the Return key:</p> </pre> <p>Then hold down the control key and press "Z", followed by the Return key.</p> -<p><a class="reference" href="#errors-and-warnings"><em>skip to the next step</em></a></p> +<p><a class="reference internal" href="#errors-and-warnings"><em>skip to the next step</em></a></p> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id26" id="or-build-from-the-command-prompt" name="or-build-from-the-command-prompt">4.2 Or, Build From the Command Prompt</a></h2> +<div class="section" id="or-build-from-the-command-prompt"> +<h2><a class="toc-backref" href="#id27">4.2 Or, Build From the Command Prompt</a></h2> <p>From your computer's <em>Start</em> menu, if you are a Visual Studio 2005 user, select</p> <blockquote> @@ -304,8 +306,8 @@ Studio 2005 user, select</p> <blockquote> <em>All Programs</em> > <em>Microsoft Visual Studio .NET 2003</em> > <em>Visual Studio .NET Tools</em> > <em>Visual Studio .NET 2003 Command Prompt</em></blockquote> -<p>to bring up a special <a class="reference" href="#command-prompt">command prompt</a> window set up for the -Visual Studio compiler. In that window, set the <a class="reference" href="#current-directory">current +<p>to bring up a special <a class="reference internal" href="#command-prompt">command prompt</a> window set up for the +Visual Studio compiler. In that window, set the <a class="reference internal" href="#current-directory">current directory</a> to a suitable location for creating some temporary files and type the following command followed by the Return key:</p> <pre class="literal-block"> @@ -319,58 +321,59 @@ echo 1 2 3 | example <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id27" id="errors-and-warnings" name="errors-and-warnings">4.3 Errors and Warnings</a></h2> +<div class="section" id="errors-and-warnings"> +<h2><a class="toc-backref" href="#id28">4.3 Errors and Warnings</a></h2> <p>Don't be alarmed if you see compiler warnings originating in Boost headers. We try to eliminate them, but doing so isn't always -practical.<a class="footnote-reference" href="#warnings" id="id6" name="id6"><sup>5</sup></a> <strong>Errors are another matter</strong>. If you're +practical.<a class="footnote-reference" href="#warnings" id="id7"><sup>5</sup></a> <strong>Errors are another matter</strong>. If you're seeing compilation errors at this point in the tutorial, check to -be sure you've copied the <a class="reference" href="#build-a-simple-program-using-boost">example program</a> correctly and that you've -correctly identified the <a class="reference" href="#boost-root-directory">Boost root directory</a>.</p> +be sure you've copied the <a class="reference internal" href="#build-a-simple-program-using-boost">example program</a> correctly and that you've +correctly identified the <a class="reference internal" href="#boost-root-directory">Boost root directory</a>.</p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id28" id="prepare-to-use-a-boost-library-binary" name="prepare-to-use-a-boost-library-binary">5 Prepare to Use a Boost Library Binary</a></h1> +<div class="section" id="prepare-to-use-a-boost-library-binary"> +<h1><a class="toc-backref" href="#id29">5 Prepare to Use a Boost Library Binary</a></h1> <p>If you want to use any of the separately-compiled Boost libraries, you'll need to acquire library binaries.</p> -<div class="section"> -<h2><a class="toc-backref" href="#id29" id="install-visual-studio-2005-or-net-2003-binaries" name="install-visual-studio-2005-or-net-2003-binaries">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></h2> -<p>The <a class="reference" href="http://www.boost-consulting.com/download/windows">installer</a> supplied by Boost Consulting will download and +<div class="section" id="install-visual-studio-2005-or-net-2003-binaries"> +<h2><a class="toc-backref" href="#id30">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></h2> +<p>The <a class="reference external" href="http://www.boost-consulting.com/download/windows">installer</a> supplied by Boost Consulting will download and install pre-compiled binaries into the <tt class="docutils literal"><span class="pre">lib\</span></tt> subdirectory of the boost root, typically <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">\lib\</span></tt>. If you installed -all variants of the <a class="reference" href="../../libs/regex/index.html">Boost.Regex</a> binary, you're done with this +all variants of the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> binary, you're done with this step. Otherwise, please run the installer again and install them now.</p> -<p><a class="reference" href="#link-your-program-to-a-boost-library"><em>skip to the next step</em></a></p> +<p><a class="reference internal" href="#link-your-program-to-a-boost-library"><em>skip to the next step</em></a></p> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id30" id="or-build-and-install-binaries-from-source" name="or-build-and-install-binaries-from-source">5.2 Or, Build and Install Binaries From Source</a></h2> +<div class="section" id="or-build-and-install-binaries-from-source"> +<h2><a class="toc-backref" href="#id31">5.2 Or, Build and Install Binaries From Source</a></h2> <p>If you're using an earlier version of Visual C++, or a compiler -from another vendor, you'll need to use <a class="reference" href="../../tools/build/index.html">Boost.Build</a> to create your +from another vendor, you'll need to use <a class="reference external" href="../../tools/build/index.html">Boost.Build</a> to create your own binaries.</p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> -<p><a class="reference" href="../../tools/build/index.html">Boost.Build</a> is a text-based system for developing, testing, and +<p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> is a text-based system for developing, testing, and installing software. To use it, you'll need an executable called <tt class="docutils literal"><span class="pre">bjam</span></tt>.</p> -<div class="section"> -<h3><a class="toc-backref" href="#id31" id="get-bjam" name="get-bjam">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> -<p><tt class="docutils literal"><span class="pre">bjam</span></tt> is the <a class="reference" href="#command-line-tool">command-line tool</a> that drives the Boost Build +<!-- .. _Boost.Jam documentation: Boost.Jam_ --> +<div class="section" id="get-bjam"> +<h3><a class="toc-backref" href="#id32">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> +<p><tt class="docutils literal"><span class="pre">bjam</span></tt> is the <a class="reference internal" href="#command-line-tool">command-line tool</a> that drives the Boost Build system. To build Boost binaries, you'll invoke <tt class="docutils literal"><span class="pre">bjam</span></tt> from the Boost root.</p> -<p>Boost provides <a class="reference" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941">pre-compiled <tt class="docutils literal"><span class="pre">bjam</span></tt> executables</a> for a variety of platforms. -Alternatively, you can build <tt class="docutils literal"><span class="pre">bjam</span></tt> yourself using <a class="reference" href="../../doc/html/jam/building.html">these +<p>Boost provides <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=72941">pre-compiled <tt class="docutils literal"><span class="pre">bjam</span></tt> executables</a> for a variety of platforms. +Alternatively, you can build <tt class="docutils literal"><span class="pre">bjam</span></tt> yourself using <a class="reference external" href="../../doc/html/jam/building.html">these instructions</a>.</p> </div> -<div class="section"> -<h3><a class="toc-backref" href="#id32" id="identify-your-toolset" name="identify-your-toolset"><span id="toolset-name"></span><span id="toolset"></span>5.2.2 Identify Your Toolset</a></h3> +<div class="section" id="identify-your-toolset"> +<span id="toolset-name"></span><span id="toolset"></span><h3><a class="toc-backref" href="#id33">5.2.2 Identify Your Toolset</a></h3> <p>First, find the toolset corresponding to your compiler in the following table.</p> -<table border="1" class="docutils table"> +<table border="1" class="docutils"> <colgroup> <col width="18%" /> <col width="33%" /> @@ -396,7 +399,7 @@ known to work well with Boost</td> <tr><td><tt class="docutils literal"><span class="pre">como</span></tt></td> <td>Comeau Computing</td> <td>Using this toolset may -require <a class="reference" href="../../tools/build/index.html">configuring</a> another +require <a class="reference external" href="../../tools/build/index.html">configuring</a> another toolset to act as its backend</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">cw</span></tt></td> @@ -468,22 +471,22 @@ affect this step in any way; you still need to select a Boost.Build toolset from the table.</p> </div> </div> -<div class="section"> -<h3><a class="toc-backref" href="#id33" id="select-a-build-directory" name="select-a-build-directory"><span id="id11"></span><span id="build-directory"></span>5.2.3 Select a Build Directory</a></h3> -<p><a class="reference" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while +<div class="section" id="select-a-build-directory"> +<span id="id12"></span><span id="build-directory"></span><h3><a class="toc-backref" href="#id34">5.2.3 Select a Build Directory</a></h3> +<p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while building into the <strong>build directory</strong>. If your Boost root directory is writable, this step isn't strictly necessary: by default Boost.Build will create a <tt class="docutils literal"><span class="pre">bin.v2/</span></tt> subdirectory for that purpose in your current working directory.</p> </div> -<div class="section"> -<h3><a class="toc-backref" href="#id34" id="invoke-bjam" name="invoke-bjam">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> +<div class="section" id="invoke-bjam"> +<h3><a class="toc-backref" href="#id35">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3> <p>Change your current directory to the Boost root directory and invoke <tt class="docutils literal"><span class="pre">bjam</span></tt> as follows:</p> <pre class="literal-block"> -bjam <strong>--build-dir=</strong><a class="reference" href="#id11"><em>build-directory</em></a> <strong>--toolset=</strong><a class="reference" href="#toolset-name"><em>toolset-name</em></a> stage +bjam <strong>--build-dir=</strong><a class="reference internal" href="#id12"><em>build-directory</em></a> <strong>--toolset=</strong><a class="reference internal" href="#toolset-name"><em>toolset-name</em></a> stage </pre> -<p>For example, your session might look like this:<a class="footnote-reference" href="#continuation" id="id12" name="id12"><sup>4</sup></a></p> +<p>For example, your session might look like this:<a class="footnote-reference" href="#continuation" id="id13"><sup>4</sup></a></p> <pre class="literal-block"> C:WINDOWS> cd <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt> <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt>> bjam <strong>^</strong> @@ -494,7 +497,7 @@ More? <strong>--toolset=</strong>msvc stage <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> <p>Boost.Build will place the Boost binaries in the <tt class="docutils literal"><span class="pre">stage</span></tt><tt class="docutils literal"><span class="pre">\</span></tt> -subdirectory of your <a class="reference" href="#build-directory">build directory</a>.</p> +subdirectory of your <a class="reference internal" href="#build-directory">build directory</a>.</p> <div class="note"> <p class="first admonition-title">Note</p> <p class="last"><tt class="docutils literal"><span class="pre">bjam</span></tt> is case-sensitive; it is important that all the @@ -515,8 +518,8 @@ be interested in:</p> </ul> </div> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id35" id="expected-build-output" name="expected-build-output">5.3 Expected Build Output</a></h2> +<div class="section" id="expected-build-output"> +<h2><a class="toc-backref" href="#id36">5.3 Expected Build Output</a></h2> <p>During the process of building Boost libraries, you can expect to see some messages printed on the console. These may include</p> <ul> @@ -539,29 +542,29 @@ look something like:</p> </li> </ul> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id36" id="in-case-of-build-errors" name="in-case-of-build-errors">5.4 In Case of Build Errors</a></h2> +<div class="section" id="in-case-of-build-errors"> +<h2><a class="toc-backref" href="#id37">5.4 In Case of Build Errors</a></h2> <p>The only error messages you see when building Boost—if any—should be related to the IOStreams library's support of zip and bzip2 -formats as described <a class="reference" href="../../libs/iostreams/doc/installation.html">here</a>. Install the relevant development +formats as described <a class="reference external" href="../../libs/iostreams/doc/installation.html">here</a>. Install the relevant development packages for libz and libbz2 if you need those features. Other errors when building Boost libraries are cause for concern.</p> <p>If it seems like the build system can't find your compiler and/or linker, consider setting up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file as described -in the <a class="reference" href="../../tools/build/index.html">Boost.Build documentation</a>. If that isn't your problem or +in the <a class="reference external" href="../../tools/build/index.html">Boost.Build documentation</a>. If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file doesn't work for you, please address questions about configuring Boost for your compiler to the -<a class="reference" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p> +<a class="reference external" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id37" id="link-your-program-to-a-boost-library" name="link-your-program-to-a-boost-library">6 Link Your Program to a Boost Library</a></h1> +<div class="section" id="link-your-program-to-a-boost-library"> +<h1><a class="toc-backref" href="#id38">6 Link Your Program to a Boost Library</a></h1> <p>To demonstrate linking with a Boost binary library, we'll use the following simple program that extracts the subject lines from -emails. It uses the <a class="reference" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a +emails. It uses the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a separately-compiled binary component.</p> <pre class="literal-block"> #include <boost/regex.hpp> @@ -599,9 +602,9 @@ information to encode the name of the correct library into your object files; the linker selects the library with that name from the directories you've told it to search.</p> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id38" id="link-from-within-the-visual-studio-ide" name="link-from-within-the-visual-studio-ide">6.1 Link From Within the Visual Studio IDE</a></h2> -<p>Starting with the <a class="reference" href="#vs-header-only">header-only example project</a> we created +<div class="section" id="link-from-within-the-visual-studio-ide"> +<h2><a class="toc-backref" href="#id39">6.1 Link From Within the Visual Studio IDE</a></h2> +<p>Starting with the <a class="reference internal" href="#vs-header-only">header-only example project</a> we created earlier:</p> <ol class="arabic simple"> <li>Right-click <strong>example</strong> in the <em>Solution Explorer</em> pane and @@ -611,10 +614,10 @@ Directories</em>, enter the path to the Boost binaries, e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">\lib\</span></tt>.</li> <li>From the <em>Build</em> menu, select <em>Build Solution</em>.</li> </ol> -<p><a class="reference" href="#test-your-program"><em>skip to the next step</em></a></p> +<p><a class="reference internal" href="#test-your-program"><em>skip to the next step</em></a></p> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id39" id="or-link-from-the-command-prompt" name="or-link-from-the-command-prompt">6.2 Or, Link From the Command Prompt</a></h2> +<div class="section" id="or-link-from-the-command-prompt"> +<h2><a class="toc-backref" href="#id40">6.2 Or, Link From the Command Prompt</a></h2> <p>For example, we can compile and link the above program from the Visual C++ command-line by simply adding the <strong>bold</strong> text below to the command line we used earlier, assuming your Boost binaries are @@ -624,12 +627,12 @@ cl /EHsc /I <em>path\to\</em><tt class="docutils literal"><span class="pre">boos <strong>/link /LIBPATH:</strong> <strong>C:\Program Files\boost\</strong><strong>boost_1_34_0</strong><strong>\lib</strong> </pre> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id40" id="library-naming" name="library-naming">6.3 Library Naming</a></h2> +<div class="section" id="library-naming"> +<h2><a class="toc-backref" href="#id41">6.3 Library Naming</a></h2> <div class="note"> <p class="first admonition-title">Note</p> <p>If, like Visual C++, your compiler supports auto-linking, -you can probably <a class="reference" href="#test-your-program"><em>skip to the next step</em></a>.</p> +you can probably <a class="reference internal" href="#test-your-program"><em>skip to the next step</em></a>.</p> <blockquote class="last"> </blockquote> </div> @@ -647,11 +650,11 @@ following elements:</p> <dd><em>Prefix</em>: except on Microsoft Windows, every Boost library name begins with this string. On Windows, only ordinary static libraries use the <tt class="docutils literal"><span class="pre">lib</span></tt> prefix; import libraries and DLLs do -not.<a class="footnote-reference" href="#distinct" id="id17" name="id17"><sup>6</sup></a></dd> +not.<a class="footnote-reference" href="#distinct" id="id18"><sup>6</sup></a></dd> <dt><tt class="docutils literal"><span class="pre">boost_regex</span></tt></dt> <dd><em>Library name</em>: all boost library filenames begin with <tt class="docutils literal"><span class="pre">boost_</span></tt>.</dd> <dt><tt class="docutils literal"><span class="pre">-vc71</span></tt></dt> -<dd><em>Toolset tag</em>: identifies the toolset and version used to build +<dd><em>Toolset tag</em>: identifies the <a class="reference internal" href="#toolset">toolset</a> and version used to build the binary.</dd> <dt><tt class="docutils literal"><span class="pre">-mt</span></tt></dt> <dd><em>Threading tag</em>: indicates that the library was @@ -663,7 +666,7 @@ of <tt class="docutils literal"><span class="pre">-mt</span></tt>.</dd> interoperability with other compiled code. For each such feature, a single letter is added to the tag:</p> <blockquote> -<table border="1" class="docutils table"> +<table border="1" class="docutils"> <colgroup> <col width="6%" /> <col width="94%" /> @@ -682,17 +685,17 @@ libraries.</td> <td>using debug versions of the standard and runtime support libraries.</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">y</span></tt></td> -<td>using a special <a class="reference" href="../../libs/python/doc/building.html#variants">debug build of Python</a>.</td> +<td>using a special <a class="reference external" href="../../libs/python/doc/building.html#variants">debug build of Python</a>.</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">d</span></tt></td> -<td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id18" name="id18"><sup>7</sup></a></td> +<td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id19"><sup>7</sup></a></td> </tr> <tr><td><tt class="docutils literal"><span class="pre">p</span></tt></td> <td>using the STLPort standard library rather than the default one supplied with your compiler.</td> </tr> <tr><td><tt class="docutils literal"><span class="pre">n</span></tt></td> -<td>using STLPort's deprecated “native iostreams” feature.<a class="footnote-reference" href="#native" id="id19" name="id19"><sup>8</sup></a></td> +<td>using STLPort's deprecated “native iostreams” feature.<a class="footnote-reference" href="#native" id="id20"><sup>8</sup></a></td> </tr> </tbody> </table> @@ -713,18 +716,19 @@ convention. On most unix-style platforms the extensions are <tt class="docutils literal"><span class="pre">.a</span></tt> and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared libraries, respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared library and (except for static libraries built by the <tt class="docutils literal"><span class="pre">gcc</span></tt> -toolset, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a +<a class="reference internal" href="#toolset">toolset</a>, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a static or import library. Where supported by toolsets on unix variants, a full version extension is added (e.g. ".so.1.34") and a symbolic link to the library file, named without the trailing version number, will also be created.</dd> </dl> +<!-- .. _Boost.Build toolset names: toolset-name_ --> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> -<div class="section"> -<h2><a class="toc-backref" href="#id41" id="test-your-program" name="test-your-program">6.4 Test Your Program</a></h2> +<div class="section" id="test-your-program"> +<h2><a class="toc-backref" href="#id42">6.4 Test Your Program</a></h2> <p>To test our subject extraction, we'll filter the following text file. Copy it out of your browser and save it as <tt class="docutils literal"><span class="pre">jayne.txt</span></tt>:</p> <pre class="literal-block"> @@ -734,7 +738,7 @@ Subject: Will Success Spoil Rock Hunter? --- See subject. </pre> -<p>Now, in a <a class="reference" href="#command-prompt">command prompt</a> window, type:</p> +<p>Now, in a <a class="reference internal" href="#command-prompt">command prompt</a> window, type:</p> <pre class="literal-block"> <em>path</em>\<em>to</em>\<em>compiled</em>\example < <em>path</em>\<em>to</em>\jayne.txt </pre> @@ -745,23 +749,23 @@ Spoil Rock Hunter?”</p> <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) --> </div> </div> -<div class="section"> -<h1><a class="toc-backref" href="#id42" id="conclusion-and-further-resources" name="conclusion-and-further-resources">7 Conclusion and Further Resources</a></h1> +<div class="section" id="conclusion-and-further-resources"> +<h1><a class="toc-backref" href="#id43">7 Conclusion and Further Resources</a></h1> <p>This concludes your introduction to Boost and to integrating it with your programs. As you start using Boost in earnest, there are surely a few additional points you'll wish we had covered. One day we may have a “Book 2 in the Getting Started series” that addresses them. Until then, we suggest you pursue the following resources. If you can't find what you need, or there's anything we can do to -make this document clearer, please post it to the <a class="reference" href="../../more/mailing_lists.htm#users">Boost Users' +make this document clearer, please post it to the <a class="reference external" href="../../more/mailing_lists.htm#users">Boost Users' mailing list</a>.</p> <ul class="simple"> -<li><a class="reference" href="../../tools/build/v2">Boost.Build reference manual</a></li> -<li><a class="reference" href="../../tools/jam/index.html">Boost.Jam reference manual</a></li> -<li><a class="reference" href="../../more/mailing_lists.htm#users">Boost Users' mailing list</a></li> -<li><a class="reference" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li> -<li><a class="reference" href="http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V2">Boost.Build Wiki</a></li> -<li><a class="reference" href="../../libs/index.html">Index of all Boost library documentation</a></li> +<li><a class="reference external" href="../../tools/build/v2">Boost.Build reference manual</a></li> +<li><a class="reference external" href="../../tools/jam/index.html">Boost.Jam reference manual</a></li> +<li><a class="reference external" href="../../more/mailing_lists.htm#users">Boost Users' mailing list</a></li> +<li><a class="reference external" href="../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li> +<li><a class="reference external" href="http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V2">Boost.Build Wiki</a></li> +<li><a class="reference external" href="../../libs/index.html">Index of all Boost library documentation</a></li> </ul> <div class="admonition-onward admonition"> <p class="first admonition-title">Onward</p> @@ -774,8 +778,8 @@ mailing list</a>.</p> <table class="docutils footnote" frame="void" id="zip" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id2" name="zip">[1]</a></td><td>If you prefer not to download executable programs, -download <a class="reference" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=376197"><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">.zip</span></tt></a> and use an external tool to decompress +<tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>If you prefer not to download executable programs, +download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041"><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">.zip</span></tt></a> and use an external tool to decompress it. We don't recommend using Windows' built-in decompression as it can be painfully slow for large archives.</td></tr> </tbody> @@ -783,7 +787,7 @@ it can be painfully slow for large archives.</td></tr> <table class="docutils footnote" frame="void" id="installer-src" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a name="installer-src">[2]</a></td><td>If you used the <a class="reference" href="http://www.boost-consulting.com/download/windows">installer</a> from Boost +<tr><td class="label">[2]</td><td>If you used the <a class="reference external" href="http://www.boost-consulting.com/download/windows">installer</a> from Boost Consulting and deselected “Source and Documentation” (it's selected by default), you won't see the <tt class="docutils literal"><span class="pre">libs/</span></tt> subdirectory. That won't affect your ability to use precompiled binaries, but @@ -793,7 +797,7 @@ you won't be able to rebuild libraries from scratch.</td></tr> <table class="docutils footnote" frame="void" id="pch" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id4" name="pch">[3]</a></td><td>There's no problem using Boost with precompiled headers; +<tr><td class="label"><a class="fn-backref" href="#id5">[3]</a></td><td>There's no problem using Boost with precompiled headers; these instructions merely avoid precompiled headers because it would require Visual Studio-specific changes to the source code used in the examples.</td></tr> @@ -802,7 +806,7 @@ used in the examples.</td></tr> <table class="docutils footnote" frame="void" id="continuation" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id12" name="continuation">[4]</a></td><td>In this example, the caret character <tt class="docutils literal"><span class="pre">^</span></tt> is a +<tr><td class="label"><a class="fn-backref" href="#id13">[4]</a></td><td>In this example, the caret character <tt class="docutils literal"><span class="pre">^</span></tt> is a way of continuing the command on multiple lines. The command prompt responds with <tt class="docutils literal"><span class="pre">More?</span></tt> to prompt for more input. Feel free to omit the carets and subsequent newlines; we used them so @@ -815,7 +819,7 @@ the example would fit on a page of reasonable width.</td></tr> <table class="docutils footnote" frame="void" id="warnings" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id6" name="warnings">[5]</a></td><td>Remember that warnings are specific to each compiler +<tr><td class="label"><a class="fn-backref" href="#id7">[5]</a></td><td>Remember that warnings are specific to each compiler implementation. The developer of a given Boost library might not have access to your compiler. Also, some warnings are extremely difficult to eliminate in generic code, to the point @@ -826,7 +830,7 @@ have any source code mechanism for suppressing warnings.</td></tr> <table class="docutils footnote" frame="void" id="distinct" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id17" name="distinct">[6]</a></td><td>This convention distinguishes the static version of +<tr><td class="label"><a class="fn-backref" href="#id18">[6]</a></td><td>This convention distinguishes the static version of a Boost library from the import library for an identically-configured Boost DLL, which would otherwise have the same name.</td></tr> @@ -835,7 +839,7 @@ same name.</td></tr> <table class="docutils footnote" frame="void" id="debug-abi" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id18" name="debug-abi">[7]</a></td><td>These libraries were compiled without optimization +<tr><td class="label"><a class="fn-backref" href="#id19">[7]</a></td><td>These libraries were compiled without optimization or inlining, with full debug symbols enabled, and without <tt class="docutils literal"><span class="pre">NDEBUG</span></tt> <tt class="docutils literal"><span class="pre">#define</span></tt>d. Although it's true that sometimes these choices don't affect binary compatibility with other @@ -845,7 +849,7 @@ compiled code, you can't count on that with Boost libraries.</td></tr> <table class="docutils footnote" frame="void" id="native" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> -<tr><td class="label"><a class="fn-backref" href="#id19" name="native">[8]</a></td><td>This feature of STLPort is deprecated because it's +<tr><td class="label"><a class="fn-backref" href="#id20">[8]</a></td><td>This feature of STLPort is deprecated because it's impossible to make it work transparently to the user; we don't recommend it.</td></tr> </tbody> |