ceph/src/boost/more/getting_started/unix-variants.html

   1 <?xml version="1.0" encoding="utf-8" ?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
   4 <head>
   5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6 <meta name="generator" content="Docutils 0.12: http://docutils.sourceforge.net/" />
   7 <title>Boost Getting Started on Unix Variants</title>
   8 <meta content="Getting Started with Boost on Unix Variants (including Linux and MacOS)" name="description" />
   9 <link rel="stylesheet" href="../../rst.css" type="text/css" />
  10 </head>
  11 <body>
  12 <div class="document" id="logo-getting-started-on-unix-variants">
  13 <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>
  14
  15 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
  16 <!-- Software License, Version 1.0. (See accompanying -->
  17 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
  18 <!-- maybe we don't need this
  19 .. Admonition:: A note to Cygwin_ and MinGW_ users
  20
  21   If you plan to build from the Cygwin_ bash shell, you're in the
  22   right place.  If you plan to use your tools from the Windows
  23   command prompt, you should follow the instructions for `getting
  24   started on Windows`_.  Other command shells, such as MinGW_\ 's
  25   MSYS, are not supported—they may or may not work.
  26
  27   .. _`Getting Started on Windows`: windows.html
  28   .. _Cygwin: http://www.cygwin.com
  29   .. _MinGW: http://mingw.org -->
  30 <div class="contents topic" id="index">
  31 <p class="topic-title first">Index</p>
  32 <ul class="auto-toc simple">
  33 <li><a class="reference internal" href="#get-boost" id="id20">1&nbsp;&nbsp;&nbsp;Get Boost</a></li>
  34 <li><a class="reference internal" href="#the-boost-distribution" id="id21">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></li>
  35 <li><a class="reference internal" href="#header-only-libraries" id="id22">3&nbsp;&nbsp;&nbsp;Header-Only Libraries</a></li>
  36 <li><a class="reference internal" href="#build-a-simple-program-using-boost" id="id23">4&nbsp;&nbsp;&nbsp;Build a Simple Program Using Boost</a><ul class="auto-toc">
  37 <li><a class="reference internal" href="#errors-and-warnings" id="id24">4.1&nbsp;&nbsp;&nbsp;Errors and Warnings</a></li>
  38 </ul>
  39 </li>
  40 <li><a class="reference internal" href="#prepare-to-use-a-boost-library-binary" id="id25">5&nbsp;&nbsp;&nbsp;Prepare to Use a Boost Library Binary</a><ul class="auto-toc">
  41 <li><a class="reference internal" href="#easy-build-and-install" id="id26">5.1&nbsp;&nbsp;&nbsp;Easy Build and Install</a></li>
  42 <li><a class="reference internal" href="#or-build-custom-binaries" id="id27">5.2&nbsp;&nbsp;&nbsp;Or, Build Custom Binaries</a><ul class="auto-toc">
  43 <li><a class="reference internal" href="#install-boost-build" id="id28">5.2.1&nbsp;&nbsp;&nbsp;Install Boost.Build</a></li>
  44 <li><a class="reference internal" href="#identify-your-toolset" id="id29">5.2.2&nbsp;&nbsp;&nbsp;Identify Your Toolset</a></li>
  45 <li><a class="reference internal" href="#select-a-build-directory" id="id30">5.2.3&nbsp;&nbsp;&nbsp;Select a Build Directory</a></li>
  46 <li><a class="reference internal" href="#invoke-b2" id="id31">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class="docutils literal">b2</tt></a></li>
  47 </ul>
  48 </li>
  49 <li><a class="reference internal" href="#expected-build-output" id="id32">5.3&nbsp;&nbsp;&nbsp;Expected Build Output</a></li>
  50 <li><a class="reference internal" href="#in-case-of-build-errors" id="id33">5.4&nbsp;&nbsp;&nbsp;In Case of Build Errors</a></li>
  51 </ul>
  52 </li>
  53 <li><a class="reference internal" href="#link-your-program-to-a-boost-library" id="id34">6&nbsp;&nbsp;&nbsp;Link Your Program to a Boost Library</a><ul class="auto-toc">
  54 <li><a class="reference internal" href="#library-naming" id="id35">6.1&nbsp;&nbsp;&nbsp;Library Naming</a></li>
  55 <li><a class="reference internal" href="#test-your-program" id="id36">6.2&nbsp;&nbsp;&nbsp;Test Your Program</a></li>
  56 </ul>
  57 </li>
  58 <li><a class="reference internal" href="#conclusion-and-further-resources" id="id37">7&nbsp;&nbsp;&nbsp;Conclusion and Further Resources</a></li>
  59 </ul>
  60 </div>
  61 <div class="section" id="get-boost">
  62 <h1><a class="toc-backref" href="#id20">1&nbsp;&nbsp;&nbsp;Get Boost</a></h1>
  63 <p>The most reliable way to get a copy of Boost is to download a
  64 distribution from <a class="reference external" href="http://www.boost.org/users/history/version_1_63_0.html">SourceForge</a>:</p>
  65 <ol class="arabic">
  66 <li><p class="first">Download <a class="reference external" href="http://www.boost.org/users/history/version_1_63_0.html"><tt class="docutils literal">boost_1_63_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p>
  67 </li>
  68 <li><p class="first">In the directory where you want to put the Boost installation,
  69 execute</p>
  70 <pre class="literal-block">
  71 tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_63_0</tt>.tar.bz2
  72 </pre>
  73 </li>
  74 </ol>
  75 <div class="admonition-other-packages admonition">
  76 <p class="first admonition-title">Other Packages</p>
  77 <p class="last">RedHat, Debian, and other distribution packagers supply Boost
  78 library packages, however you may need to adapt these
  79 instructions if you use third-party packages, because their
  80 creators usually choose to break Boost up into several packages,
  81 reorganize the directory structure of the Boost distribution,
  82 and/or rename the library binaries.<a class="footnote-reference" href="#packagers" id="id2"><sup>1</sup></a> If you have
  83 any trouble, we suggest using an official Boost distribution
  84 from <a class="reference external" href="http://www.boost.org/users/history/version_1_63_0.html">SourceForge</a>.</p>
  85 </div>
  86 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
  87 <!-- Software License, Version 1.0. (See accompanying -->
  88 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
  89 </div>
  90 <div class="section" id="the-boost-distribution">
  91 <h1><a class="toc-backref" href="#id21">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></h1>
  92 <p>This is a sketch of the resulting directory structure:</p>
  93 <pre class="literal-block">
  94 <strong>boost_1_63_0</strong><strong>/</strong> .................<em>The “boost root directory”</em>
  95    <strong>index.htm</strong> .........<em>A copy of www.boost.org starts here</em>
  96    <strong>boost</strong><strong>/</strong> .........................<em>All Boost Header files</em>
  97    <tt class="docutils literal"> </tt>
  98    <strong>libs</strong><strong>/</strong> ............<em>Tests, .cpp</em>s<em>, docs, etc., by library</em>
  99      <strong>index.html</strong> ........<em>Library documentation starts here</em>
 100      <strong>algorithm</strong><strong>/</strong>
 101      <strong>any</strong><strong>/</strong>
 102      <strong>array</strong><strong>/</strong>
 103                      <em>…more libraries…</em>
 104    <strong>status</strong><strong>/</strong> .........................<em>Boost-wide test suite</em>
 105    <strong>tools</strong><strong>/</strong> ...........<em>Utilities, e.g. Boost.Build, quickbook, bcp</em>
 106    <strong>more</strong><strong>/</strong> ..........................<em>Policy documents, etc.</em>
 107    <strong>doc</strong><strong>/</strong> ...............<em>A subset of all Boost library docs</em>
 108 </pre>
 109 <div class="sidebar">
 110 <p class="first sidebar-title">Header Organization</p>
 111 <p class="pre-wrap">The organization of Boost library headers isn't entirely uniform,
 112 but most libraries follow a few patterns:</p>
 113 <ul class="pre-wrap last">
 114 <li><p class="first">Some older libraries and most very small libraries place all
 115 public headers directly into <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt>.</p>
 116 </li>
 117 <li><p class="first">Most libraries' public headers live in a subdirectory of
 118 <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt>, named after the library.  For example, you'll find
 119 the Python library's <tt class="docutils literal">def.hpp</tt> header in</p>
 120 <pre class="literal-block">
 121 <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt><tt class="docutils literal">python</tt><tt class="docutils literal">/</tt><tt class="docutils literal">def.hpp</tt>.
 122 </pre>
 123 </li>
 124 <li><p class="first">Some libraries have an “aggregate header” in <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt> that
 125 <tt class="docutils literal">#include</tt>s all of the library's other headers.  For
 126 example, <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p>
 127 <pre class="literal-block">
 128 <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt><tt class="docutils literal">python.hpp</tt>.
 129 </pre>
 130 </li>
 131 <li><p class="first">Most libraries place private headers in a subdirectory called
 132 <tt class="docutils literal">detail</tt><tt class="docutils literal">/</tt>, or <tt class="docutils literal">aux_</tt><tt class="docutils literal">/</tt>.  Don't expect to find
 133 anything you can use in these directories.</p>
 134 </li>
 135 </ul>
 136 </div>
 137 <p>It's important to note the following:</p>
 138 <ol class="arabic" id="boost-root-directory">
 139 <li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_63_0</tt>) is
 140 sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
 141 mailing lists .</p>
 142 </li>
 143 <li><p class="first">To compile anything in Boost, you need a directory containing
 144 the <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt> subdirectory in your <tt class="docutils literal">#include</tt> path.  <tt class="docutils literal"> </tt></p>
 145 </li>
 146 <li><p class="first">Since all of Boost's header files have the <tt class="docutils literal">.hpp</tt> extension,
 147 and live in the <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt> subdirectory of the boost root, your
 148 Boost <tt class="docutils literal">#include</tt> directives will look like:</p>
 149 <pre class="literal-block">
 150 #include &lt;boost/<em>whatever</em>.hpp&gt;
 151 </pre>
 152 <p>or</p>
 153 <pre class="literal-block">
 154 #include &quot;boost/<em>whatever</em>.hpp&quot;
 155 </pre>
 156 <p>depending on your preference regarding the use of angle bracket
 157 includes.  <tt class="docutils literal"> </tt></p>
 158 </li>
 159 <li><p class="first">Don't be distracted by the <tt class="docutils literal">doc</tt><tt class="docutils literal">/</tt> subdirectory; it only
 160 contains a subset of the Boost documentation.  Start with
 161 <tt class="docutils literal">libs</tt><tt class="docutils literal">/</tt><tt class="docutils literal">index.html</tt> if you're looking for the whole enchilada.</p>
 162 </li>
 163 </ol>
 164 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 165 <!-- Software License, Version 1.0. (See accompanying -->
 166 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 167 </div>
 168 <div class="section" id="header-only-libraries">
 169 <h1><a class="toc-backref" href="#id22">3&nbsp;&nbsp;&nbsp;Header-Only Libraries</a></h1>
 170 <p>The first thing many people want to know is, “how do I build
 171 Boost?”  The good news is that often, there's nothing to build.</p>
 172 <div class="admonition-nothing-to-build admonition">
 173 <p class="first admonition-title">Nothing to Build?</p>
 174 <p class="last">Most Boost libraries are <strong>header-only</strong>: they consist <em>entirely
 175 of header files</em> containing templates and inline functions, and
 176 require no separately-compiled library binaries or special
 177 treatment when linking.</p>
 178 </div>
 179 <!-- .. _separate: -->
 180 <p>The only Boost libraries that <em>must</em> be built separately are:</p>
 181 <ul class="simple">
 182 <li><a class="reference external" href="../../libs/chrono/index.html">Boost.Chrono</a></li>
 183 <li><a class="reference external" href="../../libs/context/index.html">Boost.Context</a></li>
 184 <li><a class="reference external" href="../../libs/filesystem/index.html">Boost.Filesystem</a></li>
 185 <li><a class="reference external" href="../../libs/graph_parallel/index.html">Boost.GraphParallel</a></li>
 186 <li><a class="reference external" href="../../libs/iostreams/index.html">Boost.IOStreams</a></li>
 187 <li><a class="reference external" href="../../libs/locale/index.html">Boost.Locale</a></li>
 188 <li><a class="reference external" href="../../libs/log/index.html">Boost.Log</a> (see <a class="reference external" href="../../libs/log/doc/html/log/installation/config.html">build documentation</a>)</li>
 189 <li><a class="reference external" href="../../libs/mpi/index.html">Boost.MPI</a></li>
 190 <li><a class="reference external" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li>
 191 <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>
 192 before building and installing it)</li>
 193 <li><a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a></li>
 194 <li><a class="reference external" href="../../libs/serialization/index.html">Boost.Serialization</a></li>
 195 <li><a class="reference external" href="../../libs/signals/index.html">Boost.Signals</a></li>
 196 <li><a class="reference external" href="../../libs/system/index.html">Boost.System</a></li>
 197 <li><a class="reference external" href="../../libs/thread/index.html">Boost.Thread</a></li>
 198 <li><a class="reference external" href="../../libs/timer/index.html">Boost.Timer</a></li>
 199 <li><a class="reference external" href="../../libs/wave/index.html">Boost.Wave</a></li>
 200 </ul>
 201 <p>A few libraries have optional separately-compiled binaries:</p>
 202 <ul class="simple">
 203 <li><a class="reference external" href="../../libs/date_time/index.html">Boost.DateTime</a> has a binary component that is only needed if
 204 you're using its <tt class="docutils literal">to_string</tt>/<tt class="docutils literal">from_string</tt> or serialization
 205 features, or if you're targeting Visual C++ 6.x or Borland.</li>
 206 <li><a class="reference external" href="../../libs/graph/index.html">Boost.Graph</a> also has a binary component that is only needed if
 207 you intend to <a class="reference external" href="../../libs/graph/doc/read_graphviz.html">parse GraphViz files</a>.</li>
 208 <li><a class="reference external" href="../../libs/math/index.html">Boost.Math</a> has binary components for the TR1 and C99
 209 cmath functions.</li>
 210 <li><a class="reference external" href="../../libs/random/index.html">Boost.Random</a> has a binary component which is only needed if
 211 you're using <tt class="docutils literal">random_device</tt>.</li>
 212 <li><a class="reference external" href="../../libs/test/index.html">Boost.Test</a> can be used in “header-only” or “separately compiled”
 213 mode, although <strong>separate compilation is recommended for serious
 214 use</strong>.</li>
 215 <li><a class="reference external" href="../../libs/exception/index.html">Boost.Exception</a> provides non-intrusive implementation of
 216 exception_ptr for 32-bit _MSC_VER==1310 and _MSC_VER==1400
 217 which requires a separately-compiled binary. This is enabled by
 218 #define BOOST_ENABLE_NON_INTRUSIVE_EXCEPTION_PTR.</li>
 219 </ul>
 220 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 221 <!-- Software License, Version 1.0. (See accompanying -->
 222 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 223 </div>
 224 <div class="section" id="build-a-simple-program-using-boost">
 225 <h1><a class="toc-backref" href="#id23">4&nbsp;&nbsp;&nbsp;Build a Simple Program Using Boost</a></h1>
 226 <p>To keep things simple, let's start by using a header-only library.
 227 The following program reads a sequence of integers from standard
 228 input, uses Boost.Lambda to multiply each number by three, and
 229 writes them to standard output:</p>
 230 <pre class="literal-block">
 231 #include &lt;boost/lambda/lambda.hpp&gt;
 232 #include &lt;iostream&gt;
 233 #include &lt;iterator&gt;
 234 #include &lt;algorithm&gt;
 235
 236 int main()
 237 {
 238     using namespace boost::lambda;
 239     typedef std::istream_iterator&lt;int&gt; in;
 240
 241     std::for_each(
 242         in(std::cin), in(), std::cout &lt;&lt; (_1 * 3) &lt;&lt; &quot; &quot; );
 243 }
 244 </pre>
 245 <p>Copy the text of this program into a file called <tt class="docutils literal">example.cpp</tt>.</p>
 246 <p>Now, in the directory where you saved <tt class="docutils literal">example.cpp</tt>, issue the
 247 following command:</p>
 248 <pre class="literal-block">
 249 c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_63_0</tt> example.cpp -o example
 250 </pre>
 251 <p>To test the result, type:</p>
 252 <pre class="literal-block">
 253 echo 1 2 3 | ./example
 254 </pre>
 255 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 256 <!-- Software License, Version 1.0. (See accompanying -->
 257 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 258 <div class="section" id="errors-and-warnings">
 259 <h2><a class="toc-backref" href="#id24">4.1&nbsp;&nbsp;&nbsp;Errors and Warnings</a></h2>
 260 <p>Don't be alarmed if you see compiler warnings originating in Boost
 261 headers.  We try to eliminate them, but doing so isn't always
 262 practical.<a class="footnote-reference" href="#warnings" id="id6"><sup>3</sup></a> <strong>Errors are another matter</strong>.  If you're
 263 seeing compilation errors at this point in the tutorial, check to
 264 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
 265 correctly identified the <a class="reference internal" href="#boost-root-directory">Boost root directory</a>.</p>
 266 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 267 <!-- Software License, Version 1.0. (See accompanying -->
 268 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 269 </div>
 270 </div>
 271 <div class="section" id="prepare-to-use-a-boost-library-binary">
 272 <h1><a class="toc-backref" href="#id25">5&nbsp;&nbsp;&nbsp;Prepare to Use a Boost Library Binary</a></h1>
 273 <p>If you want to use any of the separately-compiled Boost libraries,
 274 you'll need to acquire library binaries.</p>
 275 <div class="section" id="easy-build-and-install">
 276 <h2><a class="toc-backref" href="#id26">5.1&nbsp;&nbsp;&nbsp;Easy Build and Install</a></h2>
 277 <p>Issue the following commands in the shell (don't type <tt class="docutils literal">$</tt>; that
 278 represents the shell's prompt):</p>
 279 <pre class="literal-block">
 280 <strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_63_0</tt>
 281 <strong>$</strong> ./bootstrap.sh --help
 282 </pre>
 283 <p>Select your configuration options and invoke <tt class="docutils literal">./bootstrap.sh</tt> again
 284 without the <tt class="docutils literal"><span class="pre">--help</span></tt> option.  Unless you have write permission in
 285 your system's <tt class="docutils literal">/usr/local/</tt> directory, you'll probably want to at
 286 least use</p>
 287 <pre class="literal-block">
 288 <strong>$</strong> ./bootstrap.sh <strong>--prefix=</strong><em>path</em>/<em>to</em>/<em>installation</em>/<em>prefix</em>
 289 </pre>
 290 <p>to install somewhere else.  Also, consider using the
 291 <tt class="docutils literal"><span class="pre">--show-libraries</span></tt> and <tt class="docutils literal"><span class="pre">--with-libraries=</span></tt><em>library-name-list</em> options to limit the
 292 long wait you'll experience if you build everything.  Finally,</p>
 293 <pre class="literal-block">
 294 <strong>$</strong> ./b2 install
 295 </pre>
 296 <p>will leave Boost binaries in the <tt class="docutils literal">lib/</tt> subdirectory of your
 297 installation prefix.  You will also find a copy of the Boost
 298 headers in the <tt class="docutils literal">include/</tt> subdirectory of the installation
 299 prefix, so you can henceforth use that directory as an <tt class="docutils literal">#include</tt>
 300 path in place of the Boost root directory.</p>
 301 <p><a class="reference internal" href="#link-your-program-to-a-boost-library"><em>skip to the next step</em></a></p>
 302 </div>
 303 <div class="section" id="or-build-custom-binaries">
 304 <h2><a class="toc-backref" href="#id27">5.2&nbsp;&nbsp;&nbsp;Or, Build Custom Binaries</a></h2>
 305 <p>If you're using a compiler other than your system's default, you'll
 306 need to use <a class="reference external" href="../../tools/build/index.html">Boost.Build</a> to create binaries.</p>
 307 <p>You'll also
 308 use this method if you need a nonstandard build variant (see the
 309 <a class="reference external" href="../../tools/build/index.html">Boost.Build documentation</a> for more details).</p>
 310 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 311 <!-- Software License, Version 1.0. (See accompanying -->
 312 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 313 <div class="section" id="install-boost-build">
 314 <h3><a class="toc-backref" href="#id28">5.2.1&nbsp;&nbsp;&nbsp;Install Boost.Build</a></h3>
 315 <p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> is a text-based system for developing, testing, and
 316 installing software. First, you'll need to build and
 317 install it. To do this:</p>
 318 <ol class="arabic simple">
 319 <li>Go to the directory <tt class="docutils literal">tools</tt><tt class="docutils literal">/</tt><tt class="docutils literal">build</tt><tt class="docutils literal">/</tt>.</li>
 320 <li>Run <tt class="docutils literal">bootstrap.sh</tt></li>
 321 <li>Run <tt class="docutils literal">b2 install <span class="pre">--prefix=</span></tt><em>PREFIX</em> where <em>PREFIX</em> is
 322 the directory where you want Boost.Build to be installed</li>
 323 <li>Add <em>PREFIX</em><tt class="docutils literal">/</tt><tt class="docutils literal">bin</tt> to your PATH environment variable.</li>
 324 </ol>
 325 </div>
 326 <div class="section" id="identify-your-toolset">
 327 <span id="toolset-name"></span><span id="toolset"></span><h3><a class="toc-backref" href="#id29">5.2.2&nbsp;&nbsp;&nbsp;Identify Your Toolset</a></h3>
 328 <p>First, find the toolset corresponding to your compiler in the
 329 following table (an up-to-date list is always available <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/reference/tools.html">in the
 330 Boost.Build documentation</a>).</p>
 331 <div class="note">
 332 <p class="first admonition-title">Note</p>
 333 <p class="last">If you previously chose a toolset for the purposes of
 334 <a class="reference external" href="../../doc/html/bbv2/installation.html">building b2</a>, you should assume it won't work and instead
 335 choose newly from the table below.</p>
 336 </div>
 337 <table border="1" class="docutils">
 338 <colgroup>
 339 <col width="12%" />
 340 <col width="22%" />
 341 <col width="66%" />
 342 </colgroup>
 343 <thead valign="bottom">
 344 <tr><th class="head">Toolset
 345 Name</th>
 346 <th class="head">Vendor</th>
 347 <th class="head">Notes</th>
 348 </tr>
 349 </thead>
 350 <tbody valign="top">
 351 <tr><td><tt class="docutils literal">acc</tt></td>
 352 <td>Hewlett Packard</td>
 353 <td>Only very recent versions are known to work well with Boost</td>
 354 </tr>
 355 <tr><td><tt class="docutils literal">borland</tt></td>
 356 <td>Borland</td>
 357 <td>&nbsp;</td>
 358 </tr>
 359 <tr><td><tt class="docutils literal">como</tt></td>
 360 <td>Comeau Computing</td>
 361 <td>Using this toolset may require <a class="reference external" href="../../tools/build/index.html">configuring</a> another
 362 toolset to act as its backend.</td>
 363 </tr>
 364 <tr><td><tt class="docutils literal">darwin</tt></td>
 365 <td>Apple Computer</td>
 366 <td>Apple's version of the GCC toolchain with support for
 367 Darwin and MacOS X features such as frameworks.</td>
 368 </tr>
 369 <tr><td><tt class="docutils literal">gcc</tt></td>
 370 <td>The Gnu Project</td>
 371 <td>Includes support for Cygwin and MinGW compilers.</td>
 372 </tr>
 373 <tr><td><tt class="docutils literal">hp_cxx</tt></td>
 374 <td>Hewlett Packard</td>
 375 <td>Targeted at the Tru64 operating system.</td>
 376 </tr>
 377 <tr><td><tt class="docutils literal">intel</tt></td>
 378 <td>Intel</td>
 379 <td>&nbsp;</td>
 380 </tr>
 381 <tr><td><tt class="docutils literal">msvc</tt></td>
 382 <td>Microsoft</td>
 383 <td>&nbsp;</td>
 384 </tr>
 385 <tr><td><tt class="docutils literal">sun</tt></td>
 386 <td>Oracle</td>
 387 <td>Only very recent versions are known to work well with
 388 Boost.  Note that the Oracle/Sun compiler has a large number
 389 of options which effect binary compatibility: it is vital
 390 that the libraries are built with the same options that your
 391 appliction will use. In particular be aware that the default
 392 standard library may not work well with Boost, <em>unless you
 393 are building for C++11</em>. The particular compiler options you
 394 need can be injected with the b2 command line options
 395 <tt class="docutils literal"><span class="pre">cxxflags=``and</span> ``linkflags=</tt>.  For example to build with
 396 the Apache standard library in C++03 mode use
 397 <tt class="docutils literal">b2 <span class="pre">cxxflags=-library=stdcxx4</span> <span class="pre">linkflags=-library=stdcxx4</span></tt>.</td>
 398 </tr>
 399 <tr><td><tt class="docutils literal">vacpp</tt></td>
 400 <td>IBM</td>
 401 <td>The VisualAge C++ compiler.</td>
 402 </tr>
 403 </tbody>
 404 </table>
 405 <p>If you have multiple versions of a particular compiler installed,
 406 you can append the version number to the toolset name, preceded by
 407 a hyphen, e.g. <tt class="docutils literal"><span class="pre">intel-9.0</span></tt> or
 408 <tt class="docutils literal"><span class="pre">borland-5.4.3</span></tt>. <tt class="docutils literal"> </tt></p>
 409 </div>
 410 <div class="section" id="select-a-build-directory">
 411 <span id="id11"></span><span id="build-directory"></span><h3><a class="toc-backref" href="#id30">5.2.3&nbsp;&nbsp;&nbsp;Select a Build Directory</a></h3>
 412 <p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while
 413 building into the <strong>build directory</strong>.  If your Boost root
 414 directory is writable, this step isn't strictly necessary: by
 415 default Boost.Build will create a <tt class="docutils literal">bin.v2/</tt> subdirectory for that
 416 purpose in your current working directory.</p>
 417 </div>
 418 <div class="section" id="invoke-b2">
 419 <h3><a class="toc-backref" href="#id31">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class="docutils literal">b2</tt></a></h3>
 420 <p>Change your current directory to the Boost root directory and
 421 invoke <tt class="docutils literal">b2</tt> as follows:</p>
 422 <pre class="literal-block">
 423 b2 <strong>--build-dir=</strong><a class="reference internal" href="#id11"><em>build-directory</em></a> <strong>toolset=</strong><a class="reference internal" href="#toolset-name"><em>toolset-name</em></a> <tt class="docutils literal"> </tt> stage
 424 </pre>
 425 <p>For a complete description of these and other invocation options,
 426 please see the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a>.</p>
 427 <p>For example, your session might look like this:</p>
 428 <pre class="literal-block">
 429 $ cd ~/<tt class="docutils literal">boost_1_63_0</tt>
 430 $ b2 <strong>--build-dir=</strong>/tmp/build-boost <strong>toolset=</strong>gcc stage
 431 </pre>
 432 <p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>”.</p>
 433 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 434 <!-- Software License, Version 1.0. (See accompanying -->
 435 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 436 <p>Building the special <tt class="docutils literal">stage</tt> target places Boost
 437 library binaries in the <tt class="docutils literal">stage</tt><tt class="docutils literal">/</tt><tt class="docutils literal">lib</tt><tt class="docutils literal">/</tt> subdirectory of
 438 the Boost tree.  To use a different directory pass the
 439 <tt class="docutils literal"><span class="pre">--stagedir=</span></tt><em>directory</em> option to <tt class="docutils literal">b2</tt>.</p>
 440 <div class="note">
 441 <p class="first admonition-title">Note</p>
 442 <p class="last"><tt class="docutils literal">b2</tt> is case-sensitive; it is important that all the
 443 parts shown in <strong>bold</strong> type above be entirely lower-case.</p>
 444 </div>
 445 <p>For a description of other options you can pass when invoking
 446 <tt class="docutils literal">b2</tt>, type:</p>
 447 <pre class="literal-block">
 448 b2 --help
 449 </pre>
 450 <p>In particular, to limit the amount of time spent building, you may
 451 be interested in:</p>
 452 <ul class="simple">
 453 <li>reviewing the list of library names with <tt class="docutils literal"><span class="pre">--show-libraries</span></tt></li>
 454 <li>limiting which libraries get built with the <tt class="docutils literal"><span class="pre">--with-</span></tt><em>library-name</em> or <tt class="docutils literal"><span class="pre">--without-</span></tt><em>library-name</em> options</li>
 455 <li>choosing a specific build variant by adding <tt class="docutils literal">release</tt> or
 456 <tt class="docutils literal">debug</tt> to the command line.</li>
 457 </ul>
 458 <div class="note">
 459 <p class="first admonition-title">Note</p>
 460 <p class="last">Boost.Build can produce a great deal of output, which can
 461 make it easy to miss problems.  If you want to make sure
 462 everything is went well, you might redirect the output into a
 463 file by appending “<tt class="docutils literal">&gt;build.log <span class="pre">2&gt;&amp;1</span></tt>” to your command line.</p>
 464 </div>
 465 </div>
 466 </div>
 467 <div class="section" id="expected-build-output">
 468 <h2><a class="toc-backref" href="#id32">5.3&nbsp;&nbsp;&nbsp;Expected Build Output</a></h2>
 469 <p>During the process of building Boost libraries, you can expect to
 470 see some messages printed on the console.  These may include</p>
 471 <ul>
 472 <li><p class="first">Notices about Boost library configuration—for example, the Regex
 473 library outputs a message about ICU when built without Unicode
 474 support, and the Python library may be skipped without error (but
 475 with a notice) if you don't have Python installed.</p>
 476 </li>
 477 <li><p class="first">Messages from the build tool that report the number of targets
 478 that were built or skipped.  Don't be surprised if those numbers
 479 don't make any sense to you; there are many targets per library.</p>
 480 </li>
 481 <li><p class="first">Build action messages describing what the tool is doing, which
 482 look something like:</p>
 483 <pre class="literal-block">
 484 <em>toolset-name</em>.c++ <em>long</em>/<em>path</em>/<em>to</em>/<em>file</em>/<em>being</em>/<em>built</em>
 485 </pre>
 486 </li>
 487 <li><p class="first">Compiler warnings.</p>
 488 </li>
 489 </ul>
 490 </div>
 491 <div class="section" id="in-case-of-build-errors">
 492 <h2><a class="toc-backref" href="#id33">5.4&nbsp;&nbsp;&nbsp;In Case of Build Errors</a></h2>
 493 <p>The only error messages you see when building Boost—if any—should
 494 be related to the IOStreams library's support of zip and bzip2
 495 formats as described <a class="reference external" href="../../libs/iostreams/doc/installation.html">here</a>.  Install the relevant development
 496 packages for libz and libbz2 if you need those features.  Other
 497 errors when building Boost libraries are cause for concern.</p>
 498 <p>If it seems like the build system can't find your compiler and/or
 499 linker, consider setting up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file as described
 500 <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/configuration.html">here</a>.  If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file
 501 doesn't work for you, please address questions about configuring Boost
 502 for your compiler to the <a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p>
 503 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 504 <!-- Software License, Version 1.0. (See accompanying -->
 505 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 506 </div>
 507 </div>
 508 <div class="section" id="link-your-program-to-a-boost-library">
 509 <h1><a class="toc-backref" href="#id34">6&nbsp;&nbsp;&nbsp;Link Your Program to a Boost Library</a></h1>
 510 <p>To demonstrate linking with a Boost binary library, we'll use the
 511 following simple program that extracts the subject lines from
 512 emails.  It uses the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a
 513 separately-compiled binary component.</p>
 514 <pre class="literal-block">
 515 #include &lt;boost/regex.hpp&gt;
 516 #include &lt;iostream&gt;
 517 #include &lt;string&gt;
 518
 519 int main()
 520 {
 521     std::string line;
 522     boost::regex pat( &quot;^Subject: (Re: |Aw: )*(.*)&quot; );
 523
 524     while (std::cin)
 525     {
 526         std::getline(std::cin, line);
 527         boost::smatch matches;
 528         if (boost::regex_match(line, matches, pat))
 529             std::cout &lt;&lt; matches[2] &lt;&lt; std::endl;
 530     }
 531 }
 532 </pre>
 533 <p>There are two main challenges associated with linking:</p>
 534 <ol class="arabic simple">
 535 <li>Tool configuration, e.g. choosing command-line options or IDE
 536 build settings.</li>
 537 <li>Identifying the library binary, among all the build variants,
 538 whose compile configuration is compatible with the rest of your
 539 project.</li>
 540 </ol>
 541 <p>There are two main ways to link to libraries:</p>
 542 <ol class="upperalpha">
 543 <li><p class="first">You can specify the full path to each library:</p>
 544 <pre class="literal-block">
 545 $ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_63_0</tt> example.cpp -o example <strong>\</strong>
 546    <strong>~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a</strong>
 547 </pre>
 548 </li>
 549 <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="id15"><sup>2</sup></a> dropping the filename's leading <tt class="docutils literal">lib</tt> and trailing
 550 suffix (<tt class="docutils literal">.a</tt> in this case):</p>
 551 <pre class="literal-block">
 552 $ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_63_0</tt> example.cpp -o example <strong>\</strong>
 553    <strong>-L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36</strong>
 554 </pre>
 555 <p>As you can see, this method is just as terse as method A for one
 556 library; it <em>really</em> pays off when you're using multiple
 557 libraries from the same directory.  Note, however, that if you
 558 use this method with a library that has both static (<tt class="docutils literal">.a</tt>) and
 559 dynamic (<tt class="docutils literal">.so</tt>) builds, the system may choose one
 560 automatically for you unless you pass a special option such as
 561 <tt class="docutils literal"><span class="pre">-static</span></tt> on the command line.</p>
 562 </li>
 563 </ol>
 564 <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
 565 command lines we explored earlier</a>.</p>
 566 <div class="section" id="library-naming">
 567 <h2><a class="toc-backref" href="#id35">6.1&nbsp;&nbsp;&nbsp;Library Naming</a></h2>
 568 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 569 <!-- Software License, Version 1.0. (See accompanying -->
 570 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 571 <p>In order to choose the right binary for your build configuration
 572 you need to know how Boost binaries are named.  Each library
 573 filename is composed of a common sequence of elements that describe
 574 how it was built.  For example,
 575 <tt class="docutils literal"><span class="pre">libboost_regex-vc71-mt-d-1_34.lib</span></tt> can be broken down into the
 576 following elements:</p>
 577 <dl class="docutils">
 578 <dt><tt class="docutils literal">lib</tt></dt>
 579 <dd><em>Prefix</em>: except on Microsoft Windows, every Boost library
 580 name begins with this string.  On Windows, only ordinary static
 581 libraries use the <tt class="docutils literal">lib</tt> prefix; import libraries and DLLs do
 582 not.<a class="footnote-reference" href="#distinct" id="id17"><sup>4</sup></a></dd>
 583 <dt><tt class="docutils literal">boost_regex</tt></dt>
 584 <dd><em>Library name</em>: all boost library filenames begin with <tt class="docutils literal">boost_</tt>.</dd>
 585 <dt><tt class="docutils literal"><span class="pre">-vc71</span></tt></dt>
 586 <dd><em>Toolset tag</em>: identifies the <a class="reference internal" href="#toolset">toolset</a> and version used to build
 587 the binary.</dd>
 588 <dt><tt class="docutils literal"><span class="pre">-mt</span></tt></dt>
 589 <dd><em>Threading tag</em>: indicates that the library was
 590 built with multithreading support enabled.  Libraries built
 591 without multithreading support can be identified by the absence
 592 of <tt class="docutils literal"><span class="pre">-mt</span></tt>.</dd>
 593 <dt><tt class="docutils literal"><span class="pre">-d</span></tt></dt>
 594 <dd><p class="first"><em>ABI tag</em>: encodes details that affect the library's
 595 interoperability with other compiled code.  For each such
 596 feature, a single letter is added to the tag:</p>
 597 <blockquote>
 598 <table border="1" class="docutils">
 599 <colgroup>
 600 <col width="5%" />
 601 <col width="75%" />
 602 <col width="20%" />
 603 </colgroup>
 604 <thead valign="bottom">
 605 <tr><th class="head">Key</th>
 606 <th class="head">Use this library when:</th>
 607 <th class="head">Boost.Build option</th>
 608 </tr>
 609 </thead>
 610 <tbody valign="top">
 611 <tr><td><tt class="docutils literal">s</tt></td>
 612 <td>linking statically to the C++ standard library and compiler runtime support
 613 libraries.</td>
 614 <td>runtime-link=static</td>
 615 </tr>
 616 <tr><td><tt class="docutils literal">g</tt></td>
 617 <td>using debug versions of the standard and runtime support libraries.</td>
 618 <td>runtime-debugging=on</td>
 619 </tr>
 620 <tr><td><tt class="docutils literal">y</tt></td>
 621 <td>using a special <a class="reference external" href="../../libs/python/doc/building.html#python-debugging-builds">debug build of Python</a>.</td>
 622 <td>python-debugging=on</td>
 623 </tr>
 624 <tr><td><tt class="docutils literal">d</tt></td>
 625 <td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id18"><sup>5</sup></a></td>
 626 <td>variant=debug</td>
 627 </tr>
 628 <tr><td><tt class="docutils literal">p</tt></td>
 629 <td>using the STLPort standard library rather than the default one supplied with
 630 your compiler.</td>
 631 <td>stdlib=stlport</td>
 632 </tr>
 633 </tbody>
 634 </table>
 635 </blockquote>
 636 <p class="last">For example, if you build a debug version of your code for use
 637 with debug versions of the static runtime library and the
 638 STLPort standard library in “native iostreams” mode,
 639 the tag would be: <tt class="docutils literal"><span class="pre">-sgdpn</span></tt>.  If none of the above apply, the
 640 ABI tag is ommitted.</p>
 641 </dd>
 642 <dt><tt class="docutils literal"><span class="pre">-1_34</span></tt></dt>
 643 <dd><em>Version tag</em>: the full Boost release number, with periods
 644 replaced by underscores. For example, version 1.31.1 would be
 645 tagged as &quot;-1_31_1&quot;.</dd>
 646 <dt><tt class="docutils literal">.lib</tt></dt>
 647 <dd><em>Extension</em>: determined according to the operating system's usual
 648 convention.  On most unix-style platforms the extensions are
 649 <tt class="docutils literal">.a</tt> and <tt class="docutils literal">.so</tt> for static libraries (archives) and shared
 650 libraries, respectively.  On Windows, <tt class="docutils literal">.dll</tt> indicates a shared
 651 library and <tt class="docutils literal">.lib</tt> indicates a
 652 static or import library.  Where supported by toolsets on unix
 653 variants, a full version extension is added (e.g. &quot;.so.1.34&quot;) and
 654 a symbolic link to the library file, named without the trailing
 655 version number, will also be created.</dd>
 656 </dl>
 657 <!-- .. _Boost.Build toolset names: toolset-name_ -->
 658 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 659 <!-- Software License, Version 1.0. (See accompanying -->
 660 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 661 </div>
 662 <div class="section" id="test-your-program">
 663 <h2><a class="toc-backref" href="#id36">6.2&nbsp;&nbsp;&nbsp;Test Your Program</a></h2>
 664 <p>To test our subject extraction, we'll filter the following text
 665 file.  Copy it out of your browser and save it as <tt class="docutils literal">jayne.txt</tt>:</p>
 666 <pre class="literal-block">
 667 To: George Shmidlap
 668 From: Rita Marlowe
 669 Subject: Will Success Spoil Rock Hunter?
 670 ---
 671 See subject.
 672 </pre>
 673 <p>If you linked to a shared library, you may need to prepare some
 674 platform-specific settings so that the system will be able to find
 675 and load it when your program is run.  Most platforms have an
 676 environment variable to which you can add the directory containing
 677 the library.  On many platforms (Linux, FreeBSD) that variable is
 678 <tt class="docutils literal">LD_LIBRARY_PATH</tt>, but on MacOS it's <tt class="docutils literal">DYLD_LIBRARY_PATH</tt>, and
 679 on Cygwin it's simply <tt class="docutils literal">PATH</tt>.  In most shells other than <tt class="docutils literal">csh</tt>
 680 and <tt class="docutils literal">tcsh</tt>, you can adjust the variable as follows (again, don't
 681 type the <tt class="docutils literal">$</tt>—that represents the shell prompt):</p>
 682 <pre class="literal-block">
 683 <strong>$</strong> <em>VARIABLE_NAME</em>=<em>path/to/lib/directory</em>:${<em>VARIABLE_NAME</em>}
 684 <strong>$</strong> export <em>VARIABLE_NAME</em>
 685 </pre>
 686 <p>On <tt class="docutils literal">csh</tt> and <tt class="docutils literal">tcsh</tt>, it's</p>
 687 <pre class="literal-block">
 688 <strong>$</strong> setenv <em>VARIABLE_NAME</em> <em>path/to/lib/directory</em>:${<em>VARIABLE_NAME</em>}
 689 </pre>
 690 <p>Once the necessary variable (if any) is set, you can run your
 691 program as follows:</p>
 692 <pre class="literal-block">
 693 <strong>$</strong> <em>path</em>/<em>to</em>/<em>compiled</em>/example &lt; <em>path</em>/<em>to</em>/jayne.txt
 694 </pre>
 695 <p>The program should respond with the email subject, “Will Success
 696 Spoil Rock Hunter?”</p>
 697 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 698 <!-- Software License, Version 1.0. (See accompanying -->
 699 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 700 </div>
 701 </div>
 702 <div class="section" id="conclusion-and-further-resources">
 703 <h1><a class="toc-backref" href="#id37">7&nbsp;&nbsp;&nbsp;Conclusion and Further Resources</a></h1>
 704 <p>This concludes your introduction to Boost and to integrating it
 705 with your programs.  As you start using Boost in earnest, there are
 706 surely a few additional points you'll wish we had covered.  One day
 707 we may have a “Book 2 in the Getting Started series” that addresses
 708 them.  Until then, we suggest you pursue the following resources.
 709 If you can't find what you need, or there's anything we can do to
 710 make this document clearer, please post it to the <a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#users">Boost Users'
 711 mailing list</a>.</p>
 712 <ul class="simple">
 713 <li><a class="reference external" href="../../tools/build/index.html">Boost.Build reference manual</a></li>
 714 <li><a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#users">Boost Users' mailing list</a></li>
 715 <li><a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li>
 716 <li><a class="reference external" href="../../libs/index.html">Index of all Boost library documentation</a></li>
 717 </ul>
 718 <div class="admonition-onward admonition">
 719 <p class="first admonition-title">Onward</p>
 720 <blockquote class="epigraph last">
 721 <p>Good luck, and have fun!</p>
 722 <p class="attribution">&mdash;the Boost Developers</p>
 723 </blockquote>
 724 </div>
 725 <hr class="docutils" />
 726 <table class="docutils footnote" frame="void" id="packagers" rules="none">
 727 <colgroup><col class="label" /><col /></colgroup>
 728 <tbody valign="top">
 729 <tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>If developers of Boost packages would like to work
 730 with us to make sure these instructions can be used with their
 731 packages, we'd be glad to help.  Please make your interest known
 732 to the <a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#main">Boost developers' list</a>.</td></tr>
 733 </tbody>
 734 </table>
 735 <table class="docutils footnote" frame="void" id="lowercase-l" rules="none">
 736 <colgroup><col class="label" /><col /></colgroup>
 737 <tbody valign="top">
 738 <tr><td class="label"><a class="fn-backref" href="#id15">[2]</a></td><td>That option is a dash followed by a lowercase “L”
 739 character, which looks very much like a numeral 1 in some fonts.</td></tr>
 740 </tbody>
 741 </table>
 742 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 743 <!-- Software License, Version 1.0. (See accompanying -->
 744 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 745 <table class="docutils footnote" frame="void" id="warnings" rules="none">
 746 <colgroup><col class="label" /><col /></colgroup>
 747 <tbody valign="top">
 748 <tr><td class="label"><a class="fn-backref" href="#id6">[3]</a></td><td>Remember that warnings are specific to each compiler
 749 implementation.  The developer of a given Boost library might
 750 not have access to your compiler.  Also, some warnings are
 751 extremely difficult to eliminate in generic code, to the point
 752 where it's not worth the trouble.  Finally, some compilers don't
 753 have any source code mechanism for suppressing warnings.</td></tr>
 754 </tbody>
 755 </table>
 756 <table class="docutils footnote" frame="void" id="distinct" rules="none">
 757 <colgroup><col class="label" /><col /></colgroup>
 758 <tbody valign="top">
 759 <tr><td class="label"><a class="fn-backref" href="#id17">[4]</a></td><td>This convention distinguishes the static version of
 760 a Boost library from the import library for an
 761 identically-configured Boost DLL, which would otherwise have the
 762 same name.</td></tr>
 763 </tbody>
 764 </table>
 765 <table class="docutils footnote" frame="void" id="debug-abi" rules="none">
 766 <colgroup><col class="label" /><col /></colgroup>
 767 <tbody valign="top">
 768 <tr><td class="label"><a class="fn-backref" href="#id18">[5]</a></td><td>These libraries were compiled without optimization
 769 or inlining, with full debug symbols enabled, and without
 770 <tt class="docutils literal">NDEBUG</tt> <tt class="docutils literal">#define</tt>d.  Although it's true that sometimes
 771 these choices don't affect binary compatibility with other
 772 compiled code, you can't count on that with Boost libraries.</td></tr>
 773 </tbody>
 774 </table>
 775 <table class="docutils footnote" frame="void" id="native" rules="none">
 776 <colgroup><col class="label" /><col /></colgroup>
 777 <tbody valign="top">
 778 <tr><td class="label">[6]</td><td>This feature of STLPort is deprecated because it's
 779 impossible to make it work transparently to the user; we don't
 780 recommend it.</td></tr>
 781 </tbody>
 782 </table>
 783 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 784 <!-- Software License, Version 1.0. (See accompanying -->
 785 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 786 <!-- This file contains all the definitions that need to be updated -->
 787 <!-- for each new release of Boost. -->
 788 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 789 <!-- Software License, Version 1.0. (See accompanying -->
 790 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 791 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 792 <!-- Software License, Version 1.0. (See accompanying -->
 793 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 794 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 795 <!-- Software License, Version 1.0. (See accompanying -->
 796 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 797 </div>
 798 </div>
 799 </body>
 800 </html>