ceph/src/boost/more/getting_started/windows.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 Windows</title>
   8 <link rel="stylesheet" href="../../rst.css" type="text/css" />
   9 </head>
  10 <body>
  11 <div class="document" id="logo-getting-started-on-windows">
  12 <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>
  13
  14 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
  15 <!-- Software License, Version 1.0. (See accompanying -->
  16 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
  17 <div class="admonition-a-note-to-cygwin-and-mingw-users admonition">
  18 <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>
  19 <p class="last">If you plan to use your tools from the Windows command prompt,
  20 you're in the right place.  If you plan to build from the <a class="reference external" href="http://www.cygwin.com">Cygwin</a>
  21 bash shell, you're actually running on a POSIX platform and
  22 should follow the instructions for <a class="reference external" href="unix-variants.html">getting started on Unix
  23 variants</a>.  Other command shells, such as <a class="reference external" href="http://mingw.org">MinGW</a>'s MSYS, are
  24 not supported—they may or may not work.</p>
  25 </div>
  26 <div class="contents topic" id="index">
  27 <p class="topic-title first">Index</p>
  28 <ul class="auto-toc simple">
  29 <li><a class="reference internal" href="#get-boost" id="id28">1&nbsp;&nbsp;&nbsp;Get Boost</a></li>
  30 <li><a class="reference internal" href="#the-boost-distribution" id="id29">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></li>
  31 <li><a class="reference internal" href="#header-only-libraries" id="id30">3&nbsp;&nbsp;&nbsp;Header-Only Libraries</a></li>
  32 <li><a class="reference internal" href="#build-a-simple-program-using-boost" id="id31">4&nbsp;&nbsp;&nbsp;Build a Simple Program Using Boost</a><ul class="auto-toc">
  33 <li><a class="reference internal" href="#build-from-the-visual-studio-ide" id="id32">4.1&nbsp;&nbsp;&nbsp;Build From the Visual Studio IDE</a></li>
  34 <li><a class="reference internal" href="#or-build-from-the-command-prompt" id="id33">4.2&nbsp;&nbsp;&nbsp;Or, Build From the Command Prompt</a></li>
  35 <li><a class="reference internal" href="#errors-and-warnings" id="id34">4.3&nbsp;&nbsp;&nbsp;Errors and Warnings</a></li>
  36 </ul>
  37 </li>
  38 <li><a class="reference internal" href="#prepare-to-use-a-boost-library-binary" id="id35">5&nbsp;&nbsp;&nbsp;Prepare to Use a Boost Library Binary</a><ul class="auto-toc">
  39 <li><a class="reference internal" href="#simplified-build-from-source" id="id36">5.1&nbsp;&nbsp;&nbsp;Simplified Build From Source</a></li>
  40 <li><a class="reference internal" href="#or-build-binaries-from-source" id="id37">5.2&nbsp;&nbsp;&nbsp;Or, Build Binaries From Source</a><ul class="auto-toc">
  41 <li><a class="reference internal" href="#install-boost-build" id="id38">5.2.1&nbsp;&nbsp;&nbsp;Install Boost.Build</a></li>
  42 <li><a class="reference internal" href="#identify-your-toolset" id="id39">5.2.2&nbsp;&nbsp;&nbsp;Identify Your Toolset</a></li>
  43 <li><a class="reference internal" href="#select-a-build-directory" id="id40">5.2.3&nbsp;&nbsp;&nbsp;Select a Build Directory</a></li>
  44 <li><a class="reference internal" href="#invoke-b2" id="id41">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class="docutils literal">b2</tt></a></li>
  45 </ul>
  46 </li>
  47 <li><a class="reference internal" href="#expected-build-output" id="id42">5.3&nbsp;&nbsp;&nbsp;Expected Build Output</a></li>
  48 <li><a class="reference internal" href="#in-case-of-build-errors" id="id43">5.4&nbsp;&nbsp;&nbsp;In Case of Build Errors</a></li>
  49 </ul>
  50 </li>
  51 <li><a class="reference internal" href="#link-your-program-to-a-boost-library" id="id44">6&nbsp;&nbsp;&nbsp;Link Your Program to a Boost Library</a><ul class="auto-toc">
  52 <li><a class="reference internal" href="#link-from-within-the-visual-studio-ide" id="id45">6.1&nbsp;&nbsp;&nbsp;Link From Within the Visual Studio IDE</a></li>
  53 <li><a class="reference internal" href="#or-link-from-the-command-prompt" id="id46">6.2&nbsp;&nbsp;&nbsp;Or, Link From the Command Prompt</a></li>
  54 <li><a class="reference internal" href="#library-naming" id="id47">6.3&nbsp;&nbsp;&nbsp;Library Naming</a></li>
  55 <li><a class="reference internal" href="#test-your-program" id="id48">6.4&nbsp;&nbsp;&nbsp;Test Your Program</a></li>
  56 </ul>
  57 </li>
  58 <li><a class="reference internal" href="#conclusion-and-further-resources" id="id49">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="#id28">1&nbsp;&nbsp;&nbsp;Get Boost</a></h1>
  63 <p>The most reliable way to get a copy of Boost is to
  64 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">.7z</tt></a> or <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">.zip</tt></a> and unpack it to install a complete Boost
  65 distribution.<a class="footnote-reference" href="#zip" id="id2"><sup>1</sup></a></p>
  66 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
  67 <!-- Software License, Version 1.0. (See accompanying -->
  68 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
  69 </div>
  70 <div class="section" id="the-boost-distribution">
  71 <h1><a class="toc-backref" href="#id29">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></h1>
  72 <p>This is a sketch of the resulting directory structure:</p>
  73 <pre class="literal-block">
  74 <strong>boost_1_63_0</strong><strong>\</strong> .................<em>The “boost root directory”</em>
  75    <strong>index.htm</strong> .........<em>A copy of www.boost.org starts here</em>
  76    <strong>boost</strong><strong>\</strong> .........................<em>All Boost Header files</em>
  77    <strong>lib</strong><strong>\</strong> .....................<em>precompiled library binaries</em>
  78    <strong>libs</strong><strong>\</strong> ............<em>Tests, .cpp</em>s<em>, docs, etc., by library</em>
  79      <strong>index.html</strong> ........<em>Library documentation starts here</em>
  80      <strong>algorithm</strong><strong>\</strong>
  81      <strong>any</strong><strong>\</strong>
  82      <strong>array</strong><strong>\</strong>
  83                      <em>…more libraries…</em>
  84    <strong>status</strong><strong>\</strong> .........................<em>Boost-wide test suite</em>
  85    <strong>tools</strong><strong>\</strong> ...........<em>Utilities, e.g. Boost.Build, quickbook, bcp</em>
  86    <strong>more</strong><strong>\</strong> ..........................<em>Policy documents, etc.</em>
  87    <strong>doc</strong><strong>\</strong> ...............<em>A subset of all Boost library docs</em>
  88 </pre>
  89 <div class="sidebar">
  90 <p class="first sidebar-title">Header Organization</p>
  91 <p class="pre-wrap">The organization of Boost library headers isn't entirely uniform,
  92 but most libraries follow a few patterns:</p>
  93 <ul class="pre-wrap last">
  94 <li><p class="first">Some older libraries and most very small libraries place all
  95 public headers directly into <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt>.</p>
  96 </li>
  97 <li><p class="first">Most libraries' public headers live in a subdirectory of
  98 <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt>, named after the library.  For example, you'll find
  99 the Python library's <tt class="docutils literal">def.hpp</tt> header in</p>
 100 <pre class="literal-block">
 101 <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>.
 102 </pre>
 103 </li>
 104 <li><p class="first">Some libraries have an “aggregate header” in <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt> that
 105 <tt class="docutils literal">#include</tt>s all of the library's other headers.  For
 106 example, <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p>
 107 <pre class="literal-block">
 108 <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt><tt class="docutils literal">python.hpp</tt>.
 109 </pre>
 110 </li>
 111 <li><p class="first">Most libraries place private headers in a subdirectory called
 112 <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
 113 anything you can use in these directories.</p>
 114 </li>
 115 </ul>
 116 </div>
 117 <p>It's important to note the following:</p>
 118 <ol class="arabic" id="boost-root-directory">
 119 <li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt>) is
 120 sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
 121 mailing lists .</p>
 122 </li>
 123 <li><p class="first">To compile anything in Boost, you need a directory containing
 124 the <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt> subdirectory in your <tt class="docutils literal">#include</tt> path.  Specific steps for setting up <tt class="docutils literal">#include</tt>
 125 paths in Microsoft Visual Studio follow later in this document;
 126 if you use another IDE, please consult your product's
 127 documentation for instructions.</p>
 128 </li>
 129 <li><p class="first">Since all of Boost's header files have the <tt class="docutils literal">.hpp</tt> extension,
 130 and live in the <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt> subdirectory of the boost root, your
 131 Boost <tt class="docutils literal">#include</tt> directives will look like:</p>
 132 <pre class="literal-block">
 133 #include &lt;boost/<em>whatever</em>.hpp&gt;
 134 </pre>
 135 <p>or</p>
 136 <pre class="literal-block">
 137 #include &quot;boost/<em>whatever</em>.hpp&quot;
 138 </pre>
 139 <p>depending on your preference regarding the use of angle bracket
 140 includes.  Even Windows users can (and, for
 141 portability reasons, probably should) use forward slashes in
 142 <tt class="docutils literal">#include</tt> directives; your compiler doesn't care.</p>
 143 </li>
 144 <li><p class="first">Don't be distracted by the <tt class="docutils literal">doc</tt><tt class="docutils literal">\</tt> subdirectory; it only
 145 contains a subset of the Boost documentation.  Start with
 146 <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>
 147 </li>
 148 </ol>
 149 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 150 <!-- Software License, Version 1.0. (See accompanying -->
 151 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 152 </div>
 153 <div class="section" id="header-only-libraries">
 154 <h1><a class="toc-backref" href="#id30">3&nbsp;&nbsp;&nbsp;Header-Only Libraries</a></h1>
 155 <p>The first thing many people want to know is, “how do I build
 156 Boost?”  The good news is that often, there's nothing to build.</p>
 157 <div class="admonition-nothing-to-build admonition">
 158 <p class="first admonition-title">Nothing to Build?</p>
 159 <p class="last">Most Boost libraries are <strong>header-only</strong>: they consist <em>entirely
 160 of header files</em> containing templates and inline functions, and
 161 require no separately-compiled library binaries or special
 162 treatment when linking.</p>
 163 </div>
 164 <!-- .. _separate: -->
 165 <p>The only Boost libraries that <em>must</em> be built separately are:</p>
 166 <ul class="simple">
 167 <li><a class="reference external" href="../../libs/chrono/index.html">Boost.Chrono</a></li>
 168 <li><a class="reference external" href="../../libs/context/index.html">Boost.Context</a></li>
 169 <li><a class="reference external" href="../../libs/filesystem/index.html">Boost.Filesystem</a></li>
 170 <li><a class="reference external" href="../../libs/graph_parallel/index.html">Boost.GraphParallel</a></li>
 171 <li><a class="reference external" href="../../libs/iostreams/index.html">Boost.IOStreams</a></li>
 172 <li><a class="reference external" href="../../libs/locale/index.html">Boost.Locale</a></li>
 173 <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>
 174 <li><a class="reference external" href="../../libs/mpi/index.html">Boost.MPI</a></li>
 175 <li><a class="reference external" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li>
 176 <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>
 177 before building and installing it)</li>
 178 <li><a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a></li>
 179 <li><a class="reference external" href="../../libs/serialization/index.html">Boost.Serialization</a></li>
 180 <li><a class="reference external" href="../../libs/signals/index.html">Boost.Signals</a></li>
 181 <li><a class="reference external" href="../../libs/system/index.html">Boost.System</a></li>
 182 <li><a class="reference external" href="../../libs/thread/index.html">Boost.Thread</a></li>
 183 <li><a class="reference external" href="../../libs/timer/index.html">Boost.Timer</a></li>
 184 <li><a class="reference external" href="../../libs/wave/index.html">Boost.Wave</a></li>
 185 </ul>
 186 <p>A few libraries have optional separately-compiled binaries:</p>
 187 <ul class="simple">
 188 <li><a class="reference external" href="../../libs/date_time/index.html">Boost.DateTime</a> has a binary component that is only needed if
 189 you're using its <tt class="docutils literal">to_string</tt>/<tt class="docutils literal">from_string</tt> or serialization
 190 features, or if you're targeting Visual C++ 6.x or Borland.</li>
 191 <li><a class="reference external" href="../../libs/graph/index.html">Boost.Graph</a> also has a binary component that is only needed if
 192 you intend to <a class="reference external" href="../../libs/graph/doc/read_graphviz.html">parse GraphViz files</a>.</li>
 193 <li><a class="reference external" href="../../libs/math/index.html">Boost.Math</a> has binary components for the TR1 and C99
 194 cmath functions.</li>
 195 <li><a class="reference external" href="../../libs/random/index.html">Boost.Random</a> has a binary component which is only needed if
 196 you're using <tt class="docutils literal">random_device</tt>.</li>
 197 <li><a class="reference external" href="../../libs/test/index.html">Boost.Test</a> can be used in “header-only” or “separately compiled”
 198 mode, although <strong>separate compilation is recommended for serious
 199 use</strong>.</li>
 200 <li><a class="reference external" href="../../libs/exception/index.html">Boost.Exception</a> provides non-intrusive implementation of
 201 exception_ptr for 32-bit _MSC_VER==1310 and _MSC_VER==1400
 202 which requires a separately-compiled binary. This is enabled by
 203 #define BOOST_ENABLE_NON_INTRUSIVE_EXCEPTION_PTR.</li>
 204 </ul>
 205 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 206 <!-- Software License, Version 1.0. (See accompanying -->
 207 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 208 </div>
 209 <div class="section" id="build-a-simple-program-using-boost">
 210 <h1><a class="toc-backref" href="#id31">4&nbsp;&nbsp;&nbsp;Build a Simple Program Using Boost</a></h1>
 211 <p>To keep things simple, let's start by using a header-only library.
 212 The following program reads a sequence of integers from standard
 213 input, uses Boost.Lambda to multiply each number by three, and
 214 writes them to standard output:</p>
 215 <pre class="literal-block">
 216 #include &lt;boost/lambda/lambda.hpp&gt;
 217 #include &lt;iostream&gt;
 218 #include &lt;iterator&gt;
 219 #include &lt;algorithm&gt;
 220
 221 int main()
 222 {
 223     using namespace boost::lambda;
 224     typedef std::istream_iterator&lt;int&gt; in;
 225
 226     std::for_each(
 227         in(std::cin), in(), std::cout &lt;&lt; (_1 * 3) &lt;&lt; &quot; &quot; );
 228 }
 229 </pre>
 230 <p>Copy the text of this program into a file called <tt class="docutils literal">example.cpp</tt>.</p>
 231 <div class="note" id="command-line-tool">
 232 <span id="command-prompt"></span><p class="first admonition-title">Note</p>
 233 <p class="last">To build the examples in this guide, you can use an
 234 Integrated Development Environment (IDE) like Visual Studio, or
 235 you can issue commands from the <a class="reference internal" href="#command-prompt">command prompt</a>.  Since every
 236 IDE and compiler has different options and Microsoft's are by
 237 far the dominant compilers on Windows, we only give specific
 238 directions here for Visual Studio 2005 and .NET 2003 IDEs and
 239 their respective command prompt compilers (using the command
 240 prompt is a bit simpler).  If you are using another compiler or
 241 IDE, it should be relatively easy to adapt these instructions to
 242 your environment.</p>
 243 </div>
 244 <div class="small sidebar">
 245 <p class="first sidebar-title">Command Prompt Basics</p>
 246 <p>In Windows, a command-line tool is invoked by typing its name,
 247 optionally followed by arguments, into a <em>Command Prompt</em> window
 248 and pressing the Return (or Enter) key.</p>
 249 <p>To open a generic <em>Command Prompt</em>, click the <em>Start</em> menu
 250 button, click <em>Run</em>, type “cmd”, and then click <em>OK</em>.</p>
 251 <p id="current-directory">All commands are executed within the context of a <strong>current
 252 directory</strong> in the filesystem.  To set the current directory,
 253 type:</p>
 254 <pre class="literal-block">
 255 cd <em>path</em>\<em>to</em>\<em>some</em>\<em>directory</em>
 256 </pre>
 257 <p>followed by Return.  For example,</p>
 258 <pre class="literal-block">
 259 cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt>
 260 </pre>
 261 <p class="last">Long commands can be continued across several lines by typing a
 262 caret (<tt class="docutils literal">^</tt>) at the end of all but the last line.  Some examples
 263 on this page use that technique to save horizontal space.</p>
 264 </div>
 265 <div class="section" id="build-from-the-visual-studio-ide">
 266 <span id="vs-header-only"></span><h2><a class="toc-backref" href="#id32">4.1&nbsp;&nbsp;&nbsp;Build From the Visual Studio IDE</a></h2>
 267 <ul>
 268 <li><p class="first">From Visual Studio's <em>File</em> menu, select <em>New</em> &gt; <em>Project…</em></p>
 269 </li>
 270 <li><p class="first">In the left-hand pane of the resulting <em>New Project</em> dialog,
 271 select <em>Visual C++</em> &gt; <em>Win32</em>.</p>
 272 </li>
 273 <li><p class="first">In the right-hand pane, select <em>Win32 Console Application</em>
 274 (VS8.0) or <em>Win32 Console Project</em> (VS7.1).</p>
 275 </li>
 276 <li><p class="first">In the <em>name</em> field, enter “example”</p>
 277 </li>
 278 <li><p class="first">Right-click <strong>example</strong> in the <em>Solution Explorer</em> pane and
 279 select <em>Properties</em> from the resulting pop-up menu</p>
 280 </li>
 281 <li><p class="first">In <em>Configuration Properties</em> &gt; <em>C/C++</em> &gt; <em>General</em> &gt; <em>Additional Include
 282 Directories</em>, enter the path to the Boost root directory, for example</p>
 283 <blockquote>
 284 <p><tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt></p>
 285 </blockquote>
 286 </li>
 287 <li><p class="first">In <em>Configuration Properties</em> &gt; <em>C/C++</em> &gt; <em>Precompiled Headers</em>, change
 288 <em>Use Precompiled Header (/Yu)</em> to <em>Not Using Precompiled
 289 Headers</em>.<a class="footnote-reference" href="#pch" id="id6"><sup>2</sup></a></p>
 290 </li>
 291 <li><p class="first">Replace the contents of the <tt class="docutils literal">example.cpp</tt> generated by the IDE
 292 with the example code above.</p>
 293 </li>
 294 <li><p class="first">From the <em>Build</em> menu, select <em>Build Solution</em>.</p>
 295 </li>
 296 </ul>
 297 <p>To test your application, hit the F5 key and type the following
 298 into the resulting window, followed by the Return key:</p>
 299 <pre class="literal-block">
 300 1 2 3
 301 </pre>
 302 <p>Then hold down the control key and press &quot;Z&quot;, followed by the
 303 Return key.</p>
 304 <p><a class="reference internal" href="#errors-and-warnings"><em>skip to the next step</em></a></p>
 305 </div>
 306 <div class="section" id="or-build-from-the-command-prompt">
 307 <h2><a class="toc-backref" href="#id33">4.2&nbsp;&nbsp;&nbsp;Or, Build From the Command Prompt</a></h2>
 308 <p>From your computer's <em>Start</em> menu, if you are a Visual
 309 Studio 2005 user, select</p>
 310 <blockquote>
 311 <em>All Programs</em> &gt; <em>Microsoft Visual Studio 2005</em>
 312 &gt; <em>Visual Studio Tools</em> &gt; <em>Visual Studio 2005 Command Prompt</em></blockquote>
 313 <p>or, if you're a Visual Studio .NET 2003 user, select</p>
 314 <blockquote>
 315 <em>All Programs</em> &gt; <em>Microsoft Visual Studio .NET 2003</em>
 316 &gt; <em>Visual Studio .NET Tools</em> &gt; <em>Visual Studio .NET 2003 Command Prompt</em></blockquote>
 317 <p>to bring up a special <a class="reference internal" href="#command-prompt">command prompt</a> window set up for the
 318 Visual Studio compiler.  In that window, set the <a class="reference internal" href="#current-directory">current
 319 directory</a> to a suitable location for creating some temporary
 320 files and type the following command followed by the Return key:</p>
 321 <pre class="literal-block">
 322 cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_63_0</tt> <em>path</em>\<em>to</em>\example.cpp
 323 </pre>
 324 <p>To test the result, type:</p>
 325 <pre class="literal-block">
 326 echo 1 2 3 | example
 327 </pre>
 328 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 329 <!-- Software License, Version 1.0. (See accompanying -->
 330 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 331 </div>
 332 <div class="section" id="errors-and-warnings">
 333 <h2><a class="toc-backref" href="#id34">4.3&nbsp;&nbsp;&nbsp;Errors and Warnings</a></h2>
 334 <p>Don't be alarmed if you see compiler warnings originating in Boost
 335 headers.  We try to eliminate them, but doing so isn't always
 336 practical.<a class="footnote-reference" href="#warnings" id="id8"><sup>4</sup></a> <strong>Errors are another matter</strong>.  If you're
 337 seeing compilation errors at this point in the tutorial, check to
 338 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
 339 correctly identified the <a class="reference internal" href="#boost-root-directory">Boost root directory</a>.</p>
 340 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 341 <!-- Software License, Version 1.0. (See accompanying -->
 342 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 343 </div>
 344 </div>
 345 <div class="section" id="prepare-to-use-a-boost-library-binary">
 346 <h1><a class="toc-backref" href="#id35">5&nbsp;&nbsp;&nbsp;Prepare to Use a Boost Library Binary</a></h1>
 347 <p>If you want to use any of the separately-compiled Boost libraries,
 348 you'll need to acquire library binaries.</p>
 349 <div class="section" id="simplified-build-from-source">
 350 <h2><a class="toc-backref" href="#id36">5.1&nbsp;&nbsp;&nbsp;Simplified Build From Source</a></h2>
 351 <p>If you wish to build from source with Visual C++, you can use a
 352 simple build procedure described in this section. Open the command prompt
 353 and change your current directory to the Boost root directory. Then, type
 354 the following commands:</p>
 355 <pre class="literal-block">
 356 bootstrap
 357 .\b2
 358 </pre>
 359 <p>The first command prepares the Boost.Build system for use. The second
 360 command invokes Boost.Build to build the separately-compiled Boost
 361 libraries. Please consult the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a> for a list
 362 of allowed options.</p>
 363 </div>
 364 <div class="section" id="or-build-binaries-from-source">
 365 <h2><a class="toc-backref" href="#id37">5.2&nbsp;&nbsp;&nbsp;Or, Build Binaries From Source</a></h2>
 366 <p>If you're using an earlier version of Visual C++, or a compiler
 367 from another vendor, you'll need to use <a class="reference external" href="../../tools/build/index.html">Boost.Build</a> to create your
 368 own binaries.</p>
 369 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 370 <!-- Software License, Version 1.0. (See accompanying -->
 371 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 372 <div class="section" id="install-boost-build">
 373 <h3><a class="toc-backref" href="#id38">5.2.1&nbsp;&nbsp;&nbsp;Install Boost.Build</a></h3>
 374 <p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> is a text-based system for developing, testing, and
 375 installing software. First, you'll need to build and
 376 install it. To do this:</p>
 377 <ol class="arabic simple">
 378 <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>
 379 <li>Run <tt class="docutils literal">bootstrap.bat</tt></li>
 380 <li>Run <tt class="docutils literal">b2 install <span class="pre">--prefix=</span></tt><em>PREFIX</em> where <em>PREFIX</em> is
 381 the directory where you want Boost.Build to be installed</li>
 382 <li>Add <em>PREFIX</em><tt class="docutils literal">\</tt><tt class="docutils literal">bin</tt> to your PATH environment variable.</li>
 383 </ol>
 384 </div>
 385 <div class="section" id="identify-your-toolset">
 386 <span id="toolset-name"></span><span id="toolset"></span><h3><a class="toc-backref" href="#id39">5.2.2&nbsp;&nbsp;&nbsp;Identify Your Toolset</a></h3>
 387 <p>First, find the toolset corresponding to your compiler in the
 388 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
 389 Boost.Build documentation</a>).</p>
 390 <div class="note">
 391 <p class="first admonition-title">Note</p>
 392 <p class="last">If you previously chose a toolset for the purposes of
 393 <a class="reference external" href="../../doc/html/bbv2/installation.html">building b2</a>, you should assume it won't work and instead
 394 choose newly from the table below.</p>
 395 </div>
 396 <table border="1" class="docutils">
 397 <colgroup>
 398 <col width="12%" />
 399 <col width="22%" />
 400 <col width="66%" />
 401 </colgroup>
 402 <thead valign="bottom">
 403 <tr><th class="head">Toolset
 404 Name</th>
 405 <th class="head">Vendor</th>
 406 <th class="head">Notes</th>
 407 </tr>
 408 </thead>
 409 <tbody valign="top">
 410 <tr><td><tt class="docutils literal">acc</tt></td>
 411 <td>Hewlett Packard</td>
 412 <td>Only very recent versions are known to work well with Boost</td>
 413 </tr>
 414 <tr><td><tt class="docutils literal">borland</tt></td>
 415 <td>Borland</td>
 416 <td>&nbsp;</td>
 417 </tr>
 418 <tr><td><tt class="docutils literal">como</tt></td>
 419 <td>Comeau Computing</td>
 420 <td>Using this toolset may require <a class="reference external" href="../../tools/build/index.html">configuring</a> another
 421 toolset to act as its backend.</td>
 422 </tr>
 423 <tr><td><tt class="docutils literal">darwin</tt></td>
 424 <td>Apple Computer</td>
 425 <td>Apple's version of the GCC toolchain with support for
 426 Darwin and MacOS X features such as frameworks.</td>
 427 </tr>
 428 <tr><td><tt class="docutils literal">gcc</tt></td>
 429 <td>The Gnu Project</td>
 430 <td>Includes support for Cygwin and MinGW compilers.</td>
 431 </tr>
 432 <tr><td><tt class="docutils literal">hp_cxx</tt></td>
 433 <td>Hewlett Packard</td>
 434 <td>Targeted at the Tru64 operating system.</td>
 435 </tr>
 436 <tr><td><tt class="docutils literal">intel</tt></td>
 437 <td>Intel</td>
 438 <td>&nbsp;</td>
 439 </tr>
 440 <tr><td><tt class="docutils literal">msvc</tt></td>
 441 <td>Microsoft</td>
 442 <td>&nbsp;</td>
 443 </tr>
 444 <tr><td><tt class="docutils literal">sun</tt></td>
 445 <td>Oracle</td>
 446 <td>Only very recent versions are known to work well with
 447 Boost.  Note that the Oracle/Sun compiler has a large number
 448 of options which effect binary compatibility: it is vital
 449 that the libraries are built with the same options that your
 450 appliction will use. In particular be aware that the default
 451 standard library may not work well with Boost, <em>unless you
 452 are building for C++11</em>. The particular compiler options you
 453 need can be injected with the b2 command line options
 454 <tt class="docutils literal"><span class="pre">cxxflags=``and</span> ``linkflags=</tt>.  For example to build with
 455 the Apache standard library in C++03 mode use
 456 <tt class="docutils literal">b2 <span class="pre">cxxflags=-library=stdcxx4</span> <span class="pre">linkflags=-library=stdcxx4</span></tt>.</td>
 457 </tr>
 458 <tr><td><tt class="docutils literal">vacpp</tt></td>
 459 <td>IBM</td>
 460 <td>The VisualAge C++ compiler.</td>
 461 </tr>
 462 </tbody>
 463 </table>
 464 <p>If you have multiple versions of a particular compiler installed,
 465 you can append the version number to the toolset name, preceded by
 466 a hyphen, e.g. <tt class="docutils literal"><span class="pre">intel-9.0</span></tt> or
 467 <tt class="docutils literal"><span class="pre">borland-5.4.3</span></tt>. <strong>On Windows, append a version
 468 number even if you only have one version installed</strong> (unless you
 469 are using the msvc or gcc toolsets, which have special version
 470 detection code) or <a class="reference internal" href="#auto-linking">auto-linking</a> will fail.</p>
 471 </div>
 472 <div class="section" id="select-a-build-directory">
 473 <span id="id13"></span><span id="build-directory"></span><h3><a class="toc-backref" href="#id40">5.2.3&nbsp;&nbsp;&nbsp;Select a Build Directory</a></h3>
 474 <p><a class="reference external" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while
 475 building into the <strong>build directory</strong>.  If your Boost root
 476 directory is writable, this step isn't strictly necessary: by
 477 default Boost.Build will create a <tt class="docutils literal">bin.v2/</tt> subdirectory for that
 478 purpose in your current working directory.</p>
 479 </div>
 480 <div class="section" id="invoke-b2">
 481 <h3><a class="toc-backref" href="#id41">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class="docutils literal">b2</tt></a></h3>
 482 <p>Change your current directory to the Boost root directory and
 483 invoke <tt class="docutils literal">b2</tt> as follows:</p>
 484 <pre class="literal-block">
 485 b2 <strong>--build-dir=</strong><a class="reference internal" href="#id13"><em>build-directory</em></a> <strong>toolset=</strong><a class="reference internal" href="#toolset-name"><em>toolset-name</em></a> <strong>--build-type=complete</strong> stage
 486 </pre>
 487 <p>For a complete description of these and other invocation options,
 488 please see the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a>.</p>
 489 <p>For example, your session might look like this:<a class="footnote-reference" href="#continuation" id="id15"><sup>3</sup></a></p>
 490 <pre class="literal-block">
 491 C:\WINDOWS&gt; cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt>
 492 <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt>&gt; b2 <strong>^</strong>
 493 More? <strong>--build-dir=</strong>&quot;C:\Documents and Settings\dave\build-boost&quot; <strong>^</strong>
 494 More? <strong>--build-type=complete</strong> <strong>msvc</strong> stage
 495 </pre>
 496 <p>Be sure to read <a class="reference internal" href="#continuation">this note</a> about the appearance of <tt class="docutils literal">^</tt>,
 497 <tt class="docutils literal">More?</tt> and quotation marks (<tt class="docutils literal">&quot;</tt>) in that line.</p>
 498 <p>The option “<strong>--build-type=complete</strong>” causes Boost.Build to build
 499 all supported variants of the libraries.  For instructions on how to
 500 build only specific variants, please ask on the <a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing
 501 list</a>.</p>
 502 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 503 <!-- Software License, Version 1.0. (See accompanying -->
 504 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 505 <p>Building the special <tt class="docutils literal">stage</tt> target places Boost
 506 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
 507 the Boost tree.  To use a different directory pass the
 508 <tt class="docutils literal"><span class="pre">--stagedir=</span></tt><em>directory</em> option to <tt class="docutils literal">b2</tt>.</p>
 509 <div class="note">
 510 <p class="first admonition-title">Note</p>
 511 <p class="last"><tt class="docutils literal">b2</tt> is case-sensitive; it is important that all the
 512 parts shown in <strong>bold</strong> type above be entirely lower-case.</p>
 513 </div>
 514 <p>For a description of other options you can pass when invoking
 515 <tt class="docutils literal">b2</tt>, type:</p>
 516 <pre class="literal-block">
 517 b2 --help
 518 </pre>
 519 <p>In particular, to limit the amount of time spent building, you may
 520 be interested in:</p>
 521 <ul class="simple">
 522 <li>reviewing the list of library names with <tt class="docutils literal"><span class="pre">--show-libraries</span></tt></li>
 523 <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>
 524 <li>choosing a specific build variant by adding <tt class="docutils literal">release</tt> or
 525 <tt class="docutils literal">debug</tt> to the command line.</li>
 526 </ul>
 527 <div class="note">
 528 <p class="first admonition-title">Note</p>
 529 <p class="last">Boost.Build can produce a great deal of output, which can
 530 make it easy to miss problems.  If you want to make sure
 531 everything is went well, you might redirect the output into a
 532 file by appending “<tt class="docutils literal">&gt;build.log <span class="pre">2&gt;&amp;1</span></tt>” to your command line.</p>
 533 </div>
 534 </div>
 535 </div>
 536 <div class="section" id="expected-build-output">
 537 <h2><a class="toc-backref" href="#id42">5.3&nbsp;&nbsp;&nbsp;Expected Build Output</a></h2>
 538 <p>During the process of building Boost libraries, you can expect to
 539 see some messages printed on the console.  These may include</p>
 540 <ul>
 541 <li><p class="first">Notices about Boost library configuration—for example, the Regex
 542 library outputs a message about ICU when built without Unicode
 543 support, and the Python library may be skipped without error (but
 544 with a notice) if you don't have Python installed.</p>
 545 </li>
 546 <li><p class="first">Messages from the build tool that report the number of targets
 547 that were built or skipped.  Don't be surprised if those numbers
 548 don't make any sense to you; there are many targets per library.</p>
 549 </li>
 550 <li><p class="first">Build action messages describing what the tool is doing, which
 551 look something like:</p>
 552 <pre class="literal-block">
 553 <em>toolset-name</em>.c++ <em>long</em>/<em>path</em>/<em>to</em>/<em>file</em>/<em>being</em>/<em>built</em>
 554 </pre>
 555 </li>
 556 <li><p class="first">Compiler warnings.</p>
 557 </li>
 558 </ul>
 559 </div>
 560 <div class="section" id="in-case-of-build-errors">
 561 <h2><a class="toc-backref" href="#id43">5.4&nbsp;&nbsp;&nbsp;In Case of Build Errors</a></h2>
 562 <p>The only error messages you see when building Boost—if any—should
 563 be related to the IOStreams library's support of zip and bzip2
 564 formats as described <a class="reference external" href="../../libs/iostreams/doc/installation.html">here</a>.  Install the relevant development
 565 packages for libz and libbz2 if you need those features.  Other
 566 errors when building Boost libraries are cause for concern.</p>
 567 <p>If it seems like the build system can't find your compiler and/or
 568 linker, consider setting up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file as described
 569 <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
 570 doesn't work for you, please address questions about configuring Boost
 571 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>
 572 <span class="target" id="auto-linking"></span><!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 573 <!-- Software License, Version 1.0. (See accompanying -->
 574 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 575 </div>
 576 </div>
 577 <div class="section" id="link-your-program-to-a-boost-library">
 578 <h1><a class="toc-backref" href="#id44">6&nbsp;&nbsp;&nbsp;Link Your Program to a Boost Library</a></h1>
 579 <p>To demonstrate linking with a Boost binary library, we'll use the
 580 following simple program that extracts the subject lines from
 581 emails.  It uses the <a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a
 582 separately-compiled binary component.</p>
 583 <pre class="literal-block">
 584 #include &lt;boost/regex.hpp&gt;
 585 #include &lt;iostream&gt;
 586 #include &lt;string&gt;
 587
 588 int main()
 589 {
 590     std::string line;
 591     boost::regex pat( &quot;^Subject: (Re: |Aw: )*(.*)&quot; );
 592
 593     while (std::cin)
 594     {
 595         std::getline(std::cin, line);
 596         boost::smatch matches;
 597         if (boost::regex_match(line, matches, pat))
 598             std::cout &lt;&lt; matches[2] &lt;&lt; std::endl;
 599     }
 600 }
 601 </pre>
 602 <p>There are two main challenges associated with linking:</p>
 603 <ol class="arabic simple">
 604 <li>Tool configuration, e.g. choosing command-line options or IDE
 605 build settings.</li>
 606 <li>Identifying the library binary, among all the build variants,
 607 whose compile configuration is compatible with the rest of your
 608 project.</li>
 609 </ol>
 610 <div class="admonition-auto-linking admonition">
 611 <p class="first admonition-title">Auto-Linking</p>
 612 <p>Most Windows compilers and linkers have so-called “auto-linking
 613 support,” which eliminates the second challenge.  Special code in
 614 Boost header files detects your compiler options and uses that
 615 information to encode the name of the correct library into your
 616 object files; the linker selects the library with that name from
 617 the directories you've told it to search.</p>
 618 <p class="last">The GCC toolchains (Cygwin and MinGW) are notable exceptions;
 619 GCC users should refer to the <a class="reference external" href="unix-variants.html#link-your-program-to-a-boost-library">linking instructions for Unix
 620 variant OSes</a> for the appropriate command-line options to use.</p>
 621 </div>
 622 <div class="section" id="link-from-within-the-visual-studio-ide">
 623 <h2><a class="toc-backref" href="#id45">6.1&nbsp;&nbsp;&nbsp;Link From Within the Visual Studio IDE</a></h2>
 624 <p>Starting with the <a class="reference internal" href="#vs-header-only">header-only example project</a> we created
 625 earlier:</p>
 626 <ol class="arabic simple">
 627 <li>Right-click <strong>example</strong> in the <em>Solution Explorer</em> pane and
 628 select <em>Properties</em> from the resulting pop-up menu</li>
 629 <li>In <em>Configuration Properties</em> &gt; <em>Linker</em> &gt; <em>Additional Library
 630 Directories</em>, enter the path to the Boost binaries,
 631 e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt><tt class="docutils literal">\lib\</tt>.</li>
 632 <li>From the <em>Build</em> menu, select <em>Build Solution</em>.</li>
 633 </ol>
 634 <p><a class="reference internal" href="#test-your-program"><em>skip to the next step</em></a></p>
 635 </div>
 636 <div class="section" id="or-link-from-the-command-prompt">
 637 <h2><a class="toc-backref" href="#id46">6.2&nbsp;&nbsp;&nbsp;Or, Link From the Command Prompt</a></h2>
 638 <p>For example, we can compile and link the above program from the
 639 Visual C++ command-line by simply adding the <strong>bold</strong> text below to
 640 the command line we used earlier, assuming your Boost binaries are
 641 in <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt><tt class="docutils literal">\lib</tt>:</p>
 642 <pre class="literal-block">
 643 cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_63_0</tt> example.cpp   <strong>^</strong>
 644      <strong>/link /LIBPATH:</strong><strong>C:\Program Files\boost\</strong><strong>boost_1_63_0</strong><strong>\lib</strong>
 645 </pre>
 646 </div>
 647 <div class="section" id="library-naming">
 648 <h2><a class="toc-backref" href="#id47">6.3&nbsp;&nbsp;&nbsp;Library Naming</a></h2>
 649 <div class="note">
 650 <p class="first admonition-title">Note</p>
 651 <p>If, like Visual C++, your compiler supports auto-linking,
 652 you can probably <a class="reference internal" href="#test-your-program"><em>skip to the next step</em></a>.</p>
 653 <blockquote class="last">
 654 </blockquote>
 655 </div>
 656 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 657 <!-- Software License, Version 1.0. (See accompanying -->
 658 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 659 <p>In order to choose the right binary for your build configuration
 660 you need to know how Boost binaries are named.  Each library
 661 filename is composed of a common sequence of elements that describe
 662 how it was built.  For example,
 663 <tt class="docutils literal"><span class="pre">libboost_regex-vc71-mt-d-1_34.lib</span></tt> can be broken down into the
 664 following elements:</p>
 665 <dl class="docutils">
 666 <dt><tt class="docutils literal">lib</tt></dt>
 667 <dd><em>Prefix</em>: except on Microsoft Windows, every Boost library
 668 name begins with this string.  On Windows, only ordinary static
 669 libraries use the <tt class="docutils literal">lib</tt> prefix; import libraries and DLLs do
 670 not.<a class="footnote-reference" href="#distinct" id="id23"><sup>5</sup></a></dd>
 671 <dt><tt class="docutils literal">boost_regex</tt></dt>
 672 <dd><em>Library name</em>: all boost library filenames begin with <tt class="docutils literal">boost_</tt>.</dd>
 673 <dt><tt class="docutils literal"><span class="pre">-vc71</span></tt></dt>
 674 <dd><em>Toolset tag</em>: identifies the <a class="reference internal" href="#toolset">toolset</a> and version used to build
 675 the binary.</dd>
 676 <dt><tt class="docutils literal"><span class="pre">-mt</span></tt></dt>
 677 <dd><em>Threading tag</em>: indicates that the library was
 678 built with multithreading support enabled.  Libraries built
 679 without multithreading support can be identified by the absence
 680 of <tt class="docutils literal"><span class="pre">-mt</span></tt>.</dd>
 681 <dt><tt class="docutils literal"><span class="pre">-d</span></tt></dt>
 682 <dd><p class="first"><em>ABI tag</em>: encodes details that affect the library's
 683 interoperability with other compiled code.  For each such
 684 feature, a single letter is added to the tag:</p>
 685 <blockquote>
 686 <table border="1" class="docutils">
 687 <colgroup>
 688 <col width="5%" />
 689 <col width="75%" />
 690 <col width="20%" />
 691 </colgroup>
 692 <thead valign="bottom">
 693 <tr><th class="head">Key</th>
 694 <th class="head">Use this library when:</th>
 695 <th class="head">Boost.Build option</th>
 696 </tr>
 697 </thead>
 698 <tbody valign="top">
 699 <tr><td><tt class="docutils literal">s</tt></td>
 700 <td>linking statically to the C++ standard library and compiler runtime support
 701 libraries.</td>
 702 <td>runtime-link=static</td>
 703 </tr>
 704 <tr><td><tt class="docutils literal">g</tt></td>
 705 <td>using debug versions of the standard and runtime support libraries.</td>
 706 <td>runtime-debugging=on</td>
 707 </tr>
 708 <tr><td><tt class="docutils literal">y</tt></td>
 709 <td>using a special <a class="reference external" href="../../libs/python/doc/building.html#python-debugging-builds">debug build of Python</a>.</td>
 710 <td>python-debugging=on</td>
 711 </tr>
 712 <tr><td><tt class="docutils literal">d</tt></td>
 713 <td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id24"><sup>6</sup></a></td>
 714 <td>variant=debug</td>
 715 </tr>
 716 <tr><td><tt class="docutils literal">p</tt></td>
 717 <td>using the STLPort standard library rather than the default one supplied with
 718 your compiler.</td>
 719 <td>stdlib=stlport</td>
 720 </tr>
 721 </tbody>
 722 </table>
 723 </blockquote>
 724 <p class="last">For example, if you build a debug version of your code for use
 725 with debug versions of the static runtime library and the
 726 STLPort standard library in “native iostreams” mode,
 727 the tag would be: <tt class="docutils literal"><span class="pre">-sgdpn</span></tt>.  If none of the above apply, the
 728 ABI tag is ommitted.</p>
 729 </dd>
 730 <dt><tt class="docutils literal"><span class="pre">-1_34</span></tt></dt>
 731 <dd><em>Version tag</em>: the full Boost release number, with periods
 732 replaced by underscores. For example, version 1.31.1 would be
 733 tagged as &quot;-1_31_1&quot;.</dd>
 734 <dt><tt class="docutils literal">.lib</tt></dt>
 735 <dd><em>Extension</em>: determined according to the operating system's usual
 736 convention.  On most unix-style platforms the extensions are
 737 <tt class="docutils literal">.a</tt> and <tt class="docutils literal">.so</tt> for static libraries (archives) and shared
 738 libraries, respectively.  On Windows, <tt class="docutils literal">.dll</tt> indicates a shared
 739 library and <tt class="docutils literal">.lib</tt> indicates a
 740 static or import library.  Where supported by toolsets on unix
 741 variants, a full version extension is added (e.g. &quot;.so.1.34&quot;) and
 742 a symbolic link to the library file, named without the trailing
 743 version number, will also be created.</dd>
 744 </dl>
 745 <!-- .. _Boost.Build toolset names: toolset-name_ -->
 746 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 747 <!-- Software License, Version 1.0. (See accompanying -->
 748 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 749 </div>
 750 <div class="section" id="test-your-program">
 751 <h2><a class="toc-backref" href="#id48">6.4&nbsp;&nbsp;&nbsp;Test Your Program</a></h2>
 752 <p>To test our subject extraction, we'll filter the following text
 753 file.  Copy it out of your browser and save it as <tt class="docutils literal">jayne.txt</tt>:</p>
 754 <pre class="literal-block">
 755 To: George Shmidlap
 756 From: Rita Marlowe
 757 Subject: Will Success Spoil Rock Hunter?
 758 ---
 759 See subject.
 760 </pre>
 761 <p>Now, in a <a class="reference internal" href="#command-prompt">command prompt</a> window, type:</p>
 762 <pre class="literal-block">
 763 <em>path</em>\<em>to</em>\<em>compiled</em>\example &lt; <em>path</em>\<em>to</em>\jayne.txt
 764 </pre>
 765 <p>The program should respond with the email subject, “Will Success
 766 Spoil Rock Hunter?”</p>
 767 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 768 <!-- Software License, Version 1.0. (See accompanying -->
 769 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 770 </div>
 771 </div>
 772 <div class="section" id="conclusion-and-further-resources">
 773 <h1><a class="toc-backref" href="#id49">7&nbsp;&nbsp;&nbsp;Conclusion and Further Resources</a></h1>
 774 <p>This concludes your introduction to Boost and to integrating it
 775 with your programs.  As you start using Boost in earnest, there are
 776 surely a few additional points you'll wish we had covered.  One day
 777 we may have a “Book 2 in the Getting Started series” that addresses
 778 them.  Until then, we suggest you pursue the following resources.
 779 If you can't find what you need, or there's anything we can do to
 780 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'
 781 mailing list</a>.</p>
 782 <ul class="simple">
 783 <li><a class="reference external" href="../../tools/build/index.html">Boost.Build reference manual</a></li>
 784 <li><a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#users">Boost Users' mailing list</a></li>
 785 <li><a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li>
 786 <li><a class="reference external" href="../../libs/index.html">Index of all Boost library documentation</a></li>
 787 </ul>
 788 <div class="admonition-onward admonition">
 789 <p class="first admonition-title">Onward</p>
 790 <blockquote class="epigraph last">
 791 <p>Good luck, and have fun!</p>
 792 <p class="attribution">&mdash;the Boost Developers</p>
 793 </blockquote>
 794 </div>
 795 <hr class="docutils" />
 796 <table class="docutils footnote" frame="void" id="zip" rules="none">
 797 <colgroup><col class="label" /><col /></colgroup>
 798 <tbody valign="top">
 799 <tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>We recommend
 800 downloading <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">.7z</tt></a> and using <a class="reference external" href="http://www.7-zip.org">7-Zip</a> to decompress
 801 it.  We no longer recommend .zip files for Boost because they are twice
 802 as large as the equivalent .7z files.  We don't recommend using Windows'
 803 built-in decompression as it can be painfully slow for large archives.</td></tr>
 804 </tbody>
 805 </table>
 806 <table class="docutils footnote" frame="void" id="pch" rules="none">
 807 <colgroup><col class="label" /><col /></colgroup>
 808 <tbody valign="top">
 809 <tr><td class="label"><a class="fn-backref" href="#id6">[2]</a></td><td>There's no problem using Boost with precompiled headers;
 810 these instructions merely avoid precompiled headers because it
 811 would require Visual Studio-specific changes to the source code
 812 used in the examples.</td></tr>
 813 </tbody>
 814 </table>
 815 <table class="docutils footnote" frame="void" id="continuation" rules="none">
 816 <colgroup><col class="label" /><col /></colgroup>
 817 <tbody valign="top">
 818 <tr><td class="label"><a class="fn-backref" href="#id15">[3]</a></td><td><p class="first">In this example, the caret character <tt class="docutils literal">^</tt> is a
 819 way of continuing the command on multiple lines, and must be the
 820 <strong>final character</strong> used on the line to be continued (i.e. do
 821 not follow it with spaces).  The command prompt responds with
 822 <tt class="docutils literal">More?</tt> to prompt for more input.  Feel free to omit the
 823 carets and subsequent newlines; we used them so the example
 824 would fit on a page of reasonable width.</p>
 825 <p>The command prompt treats each bit of whitespace in the command
 826 as an argument separator.  That means quotation marks (<tt class="docutils literal">&quot;</tt>)
 827 are required to keep text together whenever a single
 828 command-line argument contains spaces, as in</p>
 829 <pre class="literal-block">
 830 --build-dir=<span class="raw-html"><strong style="background-color:#B4FFB4">"</strong></span>C:\Documents<span class="raw-html"><strong style="color:#B4B4B4; background-color:#B4FFB4">_</strong></span>and<span class="raw-html"><strong style="color:#B4B4B4; background-color:#B4FFB4">_</strong></span>Settings\dave\build-boost<span class="raw-html"><strong style="background-color:#B4FFB4">"</strong></span>
 831 </pre>
 832 <p>Also, for example, you can't add spaces around the <tt class="docutils literal">=</tt> sign as in</p>
 833 <pre class="last literal-block">
 834 --build-dir<span class="raw-html"><strong style="color:#B4B4B4; background-color:#FFB4B4">_</strong></span>=<span class="raw-html"><strong style="color:#B4B4B4; background-color:#FFB4B4">_</strong></span>&quot;C:\Documents and Settings\dave\build-boost&quot;
 835 </pre>
 836 </td></tr>
 837 </tbody>
 838 </table>
 839 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 840 <!-- Software License, Version 1.0. (See accompanying -->
 841 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 842 <table class="docutils footnote" frame="void" id="warnings" rules="none">
 843 <colgroup><col class="label" /><col /></colgroup>
 844 <tbody valign="top">
 845 <tr><td class="label"><a class="fn-backref" href="#id8">[4]</a></td><td>Remember that warnings are specific to each compiler
 846 implementation.  The developer of a given Boost library might
 847 not have access to your compiler.  Also, some warnings are
 848 extremely difficult to eliminate in generic code, to the point
 849 where it's not worth the trouble.  Finally, some compilers don't
 850 have any source code mechanism for suppressing warnings.</td></tr>
 851 </tbody>
 852 </table>
 853 <table class="docutils footnote" frame="void" id="distinct" rules="none">
 854 <colgroup><col class="label" /><col /></colgroup>
 855 <tbody valign="top">
 856 <tr><td class="label"><a class="fn-backref" href="#id23">[5]</a></td><td>This convention distinguishes the static version of
 857 a Boost library from the import library for an
 858 identically-configured Boost DLL, which would otherwise have the
 859 same name.</td></tr>
 860 </tbody>
 861 </table>
 862 <table class="docutils footnote" frame="void" id="debug-abi" rules="none">
 863 <colgroup><col class="label" /><col /></colgroup>
 864 <tbody valign="top">
 865 <tr><td class="label"><a class="fn-backref" href="#id24">[6]</a></td><td>These libraries were compiled without optimization
 866 or inlining, with full debug symbols enabled, and without
 867 <tt class="docutils literal">NDEBUG</tt> <tt class="docutils literal">#define</tt>d.  Although it's true that sometimes
 868 these choices don't affect binary compatibility with other
 869 compiled code, you can't count on that with Boost libraries.</td></tr>
 870 </tbody>
 871 </table>
 872 <table class="docutils footnote" frame="void" id="native" rules="none">
 873 <colgroup><col class="label" /><col /></colgroup>
 874 <tbody valign="top">
 875 <tr><td class="label">[7]</td><td>This feature of STLPort is deprecated because it's
 876 impossible to make it work transparently to the user; we don't
 877 recommend it.</td></tr>
 878 </tbody>
 879 </table>
 880 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 881 <!-- Software License, Version 1.0. (See accompanying -->
 882 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 883 <!-- This file contains all the definitions that need to be updated -->
 884 <!-- for each new release of Boost. -->
 885 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 886 <!-- Software License, Version 1.0. (See accompanying -->
 887 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 888 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 889 <!-- Software License, Version 1.0. (See accompanying -->
 890 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 891 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 892 <!-- Software License, Version 1.0. (See accompanying -->
 893 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
 894 </div>
 895 </div>
 896 </body>
 897 </html>