mirror of
https://github.com/boostorg/more.git
synced 2025-03-23 13:10:09 +08:00
clean up some ReST errors, remove `*nix\'
[SVN r36495]
This commit is contained in:
Dave Abrahams
parent
5933328ba0
commit
c5a8b3eab6
@ -64,15 +64,15 @@ following elements:
|
||||
|
||||
``.lib``
|
||||
*Extension*: determined according to the operating system's usual
|
||||
convention. On most \*nix platforms the extensions are ``.a``
|
||||
and ``.so`` for static libraries (archives) and shared libraries,
|
||||
respectively. On Windows, ``.dll`` indicates a shared library
|
||||
and—except for static libraries built by ``gcc`` toolset, whose
|
||||
names always end in ``.a``— ``.lib`` indicates a static or import
|
||||
library. Where supported by \*nix toolsets, a full version
|
||||
extension is added (e.g. ".so.1.34") and a symbolic link to the
|
||||
library file, named without the trailing version number, will
|
||||
also be created.
|
||||
convention. On most unix-style platforms the extensions are
|
||||
``.a`` and ``.so`` for static libraries (archives) and shared
|
||||
libraries, respectively. On Windows, ``.dll`` indicates a shared
|
||||
library and (except for static libraries built by the ``gcc``
|
||||
toolset, whose names always end in ``.a``) ``.lib`` indicates a
|
||||
static or import library. Where supported by toolsets on unix
|
||||
variants, a full version extension is added (e.g. ".so.1.34") and
|
||||
a symbolic link to the library file, named without the trailing
|
||||
version number, will also be created.
|
||||
|
||||
.. _Boost.Build toolset names: toolset-name_
|
||||
|
||||
|
||||
@ -628,15 +628,15 @@ replaced by underscores. For example, version 1.31.1 would be
|
||||
tagged as "-1_31_1".</dd>
|
||||
<dt><tt class="docutils literal"><span class="pre">.lib</span></tt></dt>
|
||||
<dd><em>Extension</em>: determined according to the operating system's usual
|
||||
convention. On most *nix platforms the extensions are <tt class="docutils literal"><span class="pre">.a</span></tt>
|
||||
and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared libraries,
|
||||
respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared library
|
||||
and—except for static libraries built by <tt class="docutils literal"><span class="pre">gcc</span></tt> toolset, whose
|
||||
names always end in <tt class="docutils literal"><span class="pre">.a``—</span> <span class="pre">``.lib</span></tt> indicates a static or import
|
||||
library. Where supported by *nix toolsets, a full version
|
||||
extension is added (e.g. ".so.1.34") and a symbolic link to the
|
||||
library file, named without the trailing version number, will
|
||||
also be created.</dd>
|
||||
convention. On most unix-style platforms the extensions are
|
||||
<tt class="docutils literal"><span class="pre">.a</span></tt> and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared
|
||||
libraries, respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared
|
||||
library and (except for static libraries built by the <tt class="docutils literal"><span class="pre">gcc</span></tt>
|
||||
toolset, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a
|
||||
static or import library. Where supported by toolsets on unix
|
||||
variants, a full version extension is added (e.g. ".so.1.34") and
|
||||
a symbolic link to the library file, named without the trailing
|
||||
version number, will also be created.</dd>
|
||||
</dl>
|
||||
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
|
||||
<!-- Software License, Version 1.0. (See accompanying -->
|
||||
|
||||
@ -26,40 +26,40 @@ not supported—they may or may not work.</p>
|
||||
<div class="contents topic">
|
||||
<p class="topic-title first"><a id="index" name="index">Index</a></p>
|
||||
<ul class="auto-toc simple">
|
||||
<li><a class="reference" href="#get-boost" id="id22" name="id22">1 Get Boost</a></li>
|
||||
<li><a class="reference" href="#the-boost-distribution" id="id23" name="id23">2 The Boost Distribution</a></li>
|
||||
<li><a class="reference" href="#header-only-libraries" id="id24" name="id24">3 Header-Only Libraries</a></li>
|
||||
<li><a class="reference" href="#build-a-simple-program-using-boost" id="id25" name="id25">4 Build a Simple Program Using Boost</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#build-from-the-visual-studio-ide" id="id26" name="id26">4.1 Build From the Visual Studio IDE</a></li>
|
||||
<li><a class="reference" href="#or-build-from-the-command-prompt" id="id27" name="id27">4.2 Or, Build From the Command Prompt</a></li>
|
||||
<li><a class="reference" href="#errors-and-warnings" id="id28" name="id28">4.3 Errors and Warnings</a></li>
|
||||
<li><a class="reference" href="#get-boost" id="id21" name="id21">1 Get Boost</a></li>
|
||||
<li><a class="reference" href="#the-boost-distribution" id="id22" name="id22">2 The Boost Distribution</a></li>
|
||||
<li><a class="reference" href="#header-only-libraries" id="id23" name="id23">3 Header-Only Libraries</a></li>
|
||||
<li><a class="reference" href="#build-a-simple-program-using-boost" id="id24" name="id24">4 Build a Simple Program Using Boost</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#build-from-the-visual-studio-ide" id="id25" name="id25">4.1 Build From the Visual Studio IDE</a></li>
|
||||
<li><a class="reference" href="#or-build-from-the-command-prompt" id="id26" name="id26">4.2 Or, Build From the Command Prompt</a></li>
|
||||
<li><a class="reference" href="#errors-and-warnings" id="id27" name="id27">4.3 Errors and Warnings</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#prepare-to-use-a-boost-library-binary" id="id29" name="id29">5 Prepare to Use a Boost Library Binary</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#install-visual-studio-2005-or-net-2003-binaries" id="id30" name="id30">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></li>
|
||||
<li><a class="reference" href="#or-build-and-install-binaries-from-source" id="id31" name="id31">5.2 Or, Build and Install Binaries From Source</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#get-bjam" id="id32" name="id32">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li>
|
||||
<li><a class="reference" href="#identify-your-toolset" id="id33" name="id33">5.2.2 Identify Your Toolset</a></li>
|
||||
<li><a class="reference" href="#select-a-build-directory" id="id34" name="id34">5.2.3 Select a Build Directory</a></li>
|
||||
<li><a class="reference" href="#invoke-bjam" id="id35" name="id35">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li>
|
||||
<li><a class="reference" href="#prepare-to-use-a-boost-library-binary" id="id28" name="id28">5 Prepare to Use a Boost Library Binary</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#install-visual-studio-2005-or-net-2003-binaries" id="id29" name="id29">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></li>
|
||||
<li><a class="reference" href="#or-build-and-install-binaries-from-source" id="id30" name="id30">5.2 Or, Build and Install Binaries From Source</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#get-bjam" id="id31" name="id31">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li>
|
||||
<li><a class="reference" href="#identify-your-toolset" id="id32" name="id32">5.2.2 Identify Your Toolset</a></li>
|
||||
<li><a class="reference" href="#select-a-build-directory" id="id33" name="id33">5.2.3 Select a Build Directory</a></li>
|
||||
<li><a class="reference" href="#invoke-bjam" id="id34" name="id34">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#expected-build-output" id="id36" name="id36">5.3 Expected Build Output</a></li>
|
||||
<li><a class="reference" href="#in-case-of-build-errors" id="id37" name="id37">5.4 In Case of Build Errors</a></li>
|
||||
<li><a class="reference" href="#expected-build-output" id="id35" name="id35">5.3 Expected Build Output</a></li>
|
||||
<li><a class="reference" href="#in-case-of-build-errors" id="id36" name="id36">5.4 In Case of Build Errors</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#link-your-program-to-a-boost-library" id="id38" name="id38">6 Link Your Program to a Boost Library</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#link-from-within-the-visual-studio-ide" id="id39" name="id39">6.1 Link From Within the Visual Studio IDE</a></li>
|
||||
<li><a class="reference" href="#or-link-from-the-command-prompt" id="id40" name="id40">6.2 Or, Link From the Command Prompt</a></li>
|
||||
<li><a class="reference" href="#library-naming" id="id41" name="id41">6.3 Library Naming</a></li>
|
||||
<li><a class="reference" href="#test-your-program" id="id42" name="id42">6.4 Test Your Program</a></li>
|
||||
<li><a class="reference" href="#link-your-program-to-a-boost-library" id="id37" name="id37">6 Link Your Program to a Boost Library</a><ul class="auto-toc">
|
||||
<li><a class="reference" href="#link-from-within-the-visual-studio-ide" id="id38" name="id38">6.1 Link From Within the Visual Studio IDE</a></li>
|
||||
<li><a class="reference" href="#or-link-from-the-command-prompt" id="id39" name="id39">6.2 Or, Link From the Command Prompt</a></li>
|
||||
<li><a class="reference" href="#library-naming" id="id40" name="id40">6.3 Library Naming</a></li>
|
||||
<li><a class="reference" href="#test-your-program" id="id41" name="id41">6.4 Test Your Program</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a class="reference" href="#conclusion-and-further-resources" id="id43" name="id43">7 Conclusion and Further Resources</a></li>
|
||||
<li><a class="reference" href="#conclusion-and-further-resources" id="id42" name="id42">7 Conclusion and Further Resources</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id22" id="get-boost" name="get-boost">1 Get Boost</a></h1>
|
||||
<h1><a class="toc-backref" href="#id21" id="get-boost" name="get-boost">1 Get Boost</a></h1>
|
||||
<p>The easiest way to get a copy of Boost is to use the <a class="reference" href="http://www.boost-consulting.com/download/windows">installer</a>
|
||||
provided by <a class="reference" href="http://www.boost-consulting.com">Boost Consulting</a>. We especially recommend this
|
||||
method if you use Microsoft Visual Studio .NET 2003 or Microsoft
|
||||
@ -76,7 +76,7 @@ distribution.<a class="footnote-reference" href="#zip" id="id2" name="id2"><sup>
|
||||
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id23" id="the-boost-distribution" name="the-boost-distribution">2 The Boost Distribution</a></h1>
|
||||
<h1><a class="toc-backref" href="#id22" id="the-boost-distribution" name="the-boost-distribution">2 The Boost Distribution</a></h1>
|
||||
<p>This is is a sketch of the directory structure you'll end up with:</p>
|
||||
<pre class="literal-block">
|
||||
<strong>boost_1_34_0</strong><strong>\</strong> .................<em>The “boost root directory”</em>
|
||||
@ -159,7 +159,7 @@ contains a subset of the Boost documentation. Start with
|
||||
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id24" id="header-only-libraries" name="header-only-libraries">3 Header-Only Libraries</a></h1>
|
||||
<h1><a class="toc-backref" href="#id23" id="header-only-libraries" name="header-only-libraries">3 Header-Only Libraries</a></h1>
|
||||
<p>The first thing many people want to know is, “how do I build
|
||||
Boost?” The good news is that often, there's nothing to build.</p>
|
||||
<div class="admonition-nothing-to-build admonition">
|
||||
@ -197,7 +197,7 @@ use</strong>.</li>
|
||||
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id25" id="build-a-simple-program-using-boost" name="build-a-simple-program-using-boost">4 Build a Simple Program Using Boost</a></h1>
|
||||
<h1><a class="toc-backref" href="#id24" id="build-a-simple-program-using-boost" name="build-a-simple-program-using-boost">4 Build a Simple Program Using Boost</a></h1>
|
||||
<p>To keep things simple, let's start by using a header-only library.
|
||||
The following program reads a sequence of integers from standard
|
||||
input, uses Boost.Lambda to multiply each number by three, and
|
||||
@ -253,7 +253,7 @@ caret (<tt class="docutils literal"><span class="pre">^</span></tt>) at the end
|
||||
on this page use that technique to save horizontal space.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id26" id="build-from-the-visual-studio-ide" name="build-from-the-visual-studio-ide"><span id="vs-header-only"></span>4.1 Build From the Visual Studio IDE</a></h2>
|
||||
<h2><a class="toc-backref" href="#id25" id="build-from-the-visual-studio-ide" name="build-from-the-visual-studio-ide"><span id="vs-header-only"></span>4.1 Build From the Visual Studio IDE</a></h2>
|
||||
<ul>
|
||||
<li><p class="first">From Visual Studio's <em>File</em> menu, select <em>New</em> > <em>Project…</em></p>
|
||||
</li>
|
||||
@ -294,7 +294,7 @@ Return key.</p>
|
||||
<p><a class="reference" href="#errors-and-warnings"><em>skip to the next step</em></a></p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id27" id="or-build-from-the-command-prompt" name="or-build-from-the-command-prompt">4.2 Or, Build From the Command Prompt</a></h2>
|
||||
<h2><a class="toc-backref" href="#id26" id="or-build-from-the-command-prompt" name="or-build-from-the-command-prompt">4.2 Or, Build From the Command Prompt</a></h2>
|
||||
<p>From your computer's <em>Start</em> menu, if you are a Visual
|
||||
Studio 2005 user, select</p>
|
||||
<blockquote>
|
||||
@ -320,7 +320,7 @@ echo 1 2 3 | example
|
||||
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id28" id="errors-and-warnings" name="errors-and-warnings">4.3 Errors and Warnings</a></h2>
|
||||
<h2><a class="toc-backref" href="#id27" id="errors-and-warnings" name="errors-and-warnings">4.3 Errors and Warnings</a></h2>
|
||||
<p>Don't be alarmed if you see compiler warnings originating in Boost
|
||||
headers. We try to eliminate them, but doing so isn't always
|
||||
practical.<a class="footnote-reference" href="#warnings" id="id6" name="id6"><sup>5</sup></a> <strong>Errors are another matter</strong>. If you're
|
||||
@ -333,11 +333,11 @@ correctly identified the <a class="reference" href="#boost-root-directory">Boost
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id29" id="prepare-to-use-a-boost-library-binary" name="prepare-to-use-a-boost-library-binary">5 Prepare to Use a Boost Library Binary</a></h1>
|
||||
<h1><a class="toc-backref" href="#id28" id="prepare-to-use-a-boost-library-binary" name="prepare-to-use-a-boost-library-binary">5 Prepare to Use a Boost Library Binary</a></h1>
|
||||
<p>If you want to use any of the separately-compiled Boost libraries,
|
||||
you'll need to acquire library binaries.</p>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id30" id="install-visual-studio-2005-or-net-2003-binaries" name="install-visual-studio-2005-or-net-2003-binaries">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></h2>
|
||||
<h2><a class="toc-backref" href="#id29" id="install-visual-studio-2005-or-net-2003-binaries" name="install-visual-studio-2005-or-net-2003-binaries">5.1 Install Visual Studio (2005 or .NET 2003) Binaries</a></h2>
|
||||
<p>The <a class="reference" href="http://www.boost-consulting.com/download/windows">installer</a> supplied by Boost Consulting will download and
|
||||
install pre-compiled binaries into the <tt class="docutils literal"><span class="pre">lib\</span></tt> subdirectory of the
|
||||
boost root, typically <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt><tt class="docutils literal"><span class="pre">\lib\</span></tt>. If you installed
|
||||
@ -347,7 +347,7 @@ now.</p>
|
||||
<p><a class="reference" href="#link-your-program-to-a-boost-library"><em>skip to the next step</em></a></p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id31" id="or-build-and-install-binaries-from-source" name="or-build-and-install-binaries-from-source">5.2 Or, Build and Install Binaries From Source</a></h2>
|
||||
<h2><a class="toc-backref" href="#id30" id="or-build-and-install-binaries-from-source" name="or-build-and-install-binaries-from-source">5.2 Or, Build and Install Binaries From Source</a></h2>
|
||||
<p>If you're using an earlier version of Visual C++, or a compiler
|
||||
from another vendor, you'll need to use <a class="reference" href="../../tools/build/index.html">Boost.Build</a> to create your
|
||||
own binaries.</p>
|
||||
@ -358,7 +358,7 @@ own binaries.</p>
|
||||
installing software. To use it, you'll need an executable called
|
||||
<tt class="docutils literal"><span class="pre">bjam</span></tt>.</p>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id32" id="get-bjam" name="get-bjam">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3>
|
||||
<h3><a class="toc-backref" href="#id31" id="get-bjam" name="get-bjam">5.2.1 Get <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3>
|
||||
<p><tt class="docutils literal"><span class="pre">bjam</span></tt> is the <a class="reference" href="#command-line-tool">command-line tool</a> that drives the Boost Build
|
||||
system. To build Boost binaries, you'll invoke <tt class="docutils literal"><span class="pre">bjam</span></tt> from the
|
||||
Boost root.</p>
|
||||
@ -367,7 +367,7 @@ Alternatively, you can build <tt class="docutils literal"><span class="pre">bjam
|
||||
instructions</a>.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id33" id="identify-your-toolset" name="identify-your-toolset"><span id="toolset-name"></span><span id="toolset"></span>5.2.2 Identify Your Toolset</a></h3>
|
||||
<h3><a class="toc-backref" href="#id32" id="identify-your-toolset" name="identify-your-toolset"><span id="toolset-name"></span><span id="toolset"></span>5.2.2 Identify Your Toolset</a></h3>
|
||||
<p>First, find the toolset corresponding to your compiler in the
|
||||
following table.</p>
|
||||
<table border="1" class="docutils table">
|
||||
@ -469,7 +469,7 @@ toolset from the table.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id34" id="select-a-build-directory" name="select-a-build-directory"><span id="id11"></span><span id="build-directory"></span>5.2.3 Select a Build Directory</a></h3>
|
||||
<h3><a class="toc-backref" href="#id33" id="select-a-build-directory" name="select-a-build-directory"><span id="id11"></span><span id="build-directory"></span>5.2.3 Select a Build Directory</a></h3>
|
||||
<p><a class="reference" href="../../tools/build/index.html">Boost.Build</a> will place all intermediate files it generates while
|
||||
building into the <strong>build directory</strong>. If your Boost root
|
||||
directory is writable, this step isn't strictly necessary: by
|
||||
@ -477,7 +477,7 @@ default Boost.Build will create a <tt class="docutils literal"><span class="pre"
|
||||
purpose in your current working directory.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h3><a class="toc-backref" href="#id35" id="invoke-bjam" name="invoke-bjam">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3>
|
||||
<h3><a class="toc-backref" href="#id34" id="invoke-bjam" name="invoke-bjam">5.2.4 Invoke <tt class="docutils literal"><span class="pre">bjam</span></tt></a></h3>
|
||||
<p>Change your current directory to the Boost root directory and
|
||||
invoke <tt class="docutils literal"><span class="pre">bjam</span></tt> as follows:</p>
|
||||
<pre class="literal-block">
|
||||
@ -516,7 +516,7 @@ be interested in:</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id36" id="expected-build-output" name="expected-build-output">5.3 Expected Build Output</a></h2>
|
||||
<h2><a class="toc-backref" href="#id35" id="expected-build-output" name="expected-build-output">5.3 Expected Build Output</a></h2>
|
||||
<p>During the process of building Boost libraries, you can expect to
|
||||
see some messages printed on the console. These may include</p>
|
||||
<ul>
|
||||
@ -540,7 +540,7 @@ look something like:</p>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id37" id="in-case-of-build-errors" name="in-case-of-build-errors">5.4 In Case of Build Errors</a></h2>
|
||||
<h2><a class="toc-backref" href="#id36" id="in-case-of-build-errors" name="in-case-of-build-errors">5.4 In Case of Build Errors</a></h2>
|
||||
<p>The only error messages you see when building Boost—if any—should
|
||||
be related to the IOStreams library's support of zip and bzip2
|
||||
formats as described <a class="reference" href="../../libs/iostreams/doc/installation.html">here</a>. Install the relevant development
|
||||
@ -558,7 +558,7 @@ questions about configuring Boost for your compiler to the
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id38" id="link-your-program-to-a-boost-library" name="link-your-program-to-a-boost-library">6 Link Your Program to a Boost Library</a></h1>
|
||||
<h1><a class="toc-backref" href="#id37" id="link-your-program-to-a-boost-library" name="link-your-program-to-a-boost-library">6 Link Your Program to a Boost Library</a></h1>
|
||||
<p>To demonstrate linking with a Boost binary library, we'll use the
|
||||
following simple program that extracts the subject lines from
|
||||
emails. It uses the <a class="reference" href="../../libs/regex/index.html">Boost.Regex</a> library, which has a
|
||||
@ -600,7 +600,7 @@ object files; the linker selects the library with that name from
|
||||
the directories you've told it to search.</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id39" id="link-from-within-the-visual-studio-ide" name="link-from-within-the-visual-studio-ide">6.1 Link From Within the Visual Studio IDE</a></h2>
|
||||
<h2><a class="toc-backref" href="#id38" id="link-from-within-the-visual-studio-ide" name="link-from-within-the-visual-studio-ide">6.1 Link From Within the Visual Studio IDE</a></h2>
|
||||
<p>Starting with the <a class="reference" href="#vs-header-only">header-only example project</a> we created
|
||||
earlier:</p>
|
||||
<ol class="arabic simple">
|
||||
@ -614,7 +614,7 @@ e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> <span clas
|
||||
<p><a class="reference" href="#test-your-program"><em>skip to the next step</em></a></p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id40" id="or-link-from-the-command-prompt" name="or-link-from-the-command-prompt">6.2 Or, Link From the Command Prompt</a></h2>
|
||||
<h2><a class="toc-backref" href="#id39" id="or-link-from-the-command-prompt" name="or-link-from-the-command-prompt">6.2 Or, Link From the Command Prompt</a></h2>
|
||||
<p>For example, we can compile and link the above program from the
|
||||
Visual C++ command-line by simply adding the <strong>bold</strong> text below to
|
||||
the command line we used earlier, assuming your Boost binaries are
|
||||
@ -623,15 +623,9 @@ in <tt class="docutils literal"><span class="pre">C:\Program</span> <span class=
|
||||
cl /EHsc /I <em>path\to\</em><tt class="docutils literal"><span class="pre">boost_1_34_0</span></tt> example.cpp <strong>^</strong>
|
||||
<strong>/link /LIBPATH:</strong> <strong>C:\Program Files\boost\</strong><strong>boost_1_34_0</strong><strong>\lib</strong>
|
||||
</pre>
|
||||
<div class="note">
|
||||
<p class="first admonition-title">Note</p>
|
||||
<p>If—like Visual C++—your compiler supports auto-linking,
|
||||
you can probably ignore the next section.</p>
|
||||
<p class="last"><a class="reference" href="#test-your-program"><em>skip to the next step</em></a></p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id41" id="library-naming" name="library-naming">6.3 Library Naming</a></h2>
|
||||
<h2><a class="toc-backref" href="#id40" id="library-naming" name="library-naming">6.3 Library Naming</a></h2>
|
||||
<div class="note">
|
||||
<p class="first admonition-title">Note</p>
|
||||
<p>If, like Visual C++, your compiler supports auto-linking,
|
||||
@ -653,7 +647,7 @@ following elements:</p>
|
||||
<dd><em>Prefix</em>: except on Microsoft Windows, every Boost library
|
||||
name begins with this string. On Windows, only ordinary static
|
||||
libraries use the <tt class="docutils literal"><span class="pre">lib</span></tt> prefix; import libraries and DLLs do
|
||||
not.<a class="footnote-reference" href="#distinct" id="id18" name="id18"><sup>6</sup></a></dd>
|
||||
not.<a class="footnote-reference" href="#distinct" id="id17" name="id17"><sup>6</sup></a></dd>
|
||||
<dt><tt class="docutils literal"><span class="pre">boost_regex</span></tt></dt>
|
||||
<dd><em>Library name</em>: all boost library filenames begin with <tt class="docutils literal"><span class="pre">boost_</span></tt>.</dd>
|
||||
<dt><tt class="docutils literal"><span class="pre">-vc71</span></tt></dt>
|
||||
@ -691,14 +685,14 @@ libraries.</td>
|
||||
<td>using a special <a class="reference" href="../../libs/python/doc/building.html#variants">debug build of Python</a>.</td>
|
||||
</tr>
|
||||
<tr><td><tt class="docutils literal"><span class="pre">d</span></tt></td>
|
||||
<td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id19" name="id19"><sup>7</sup></a></td>
|
||||
<td>building a debug version of your code.<a class="footnote-reference" href="#debug-abi" id="id18" name="id18"><sup>7</sup></a></td>
|
||||
</tr>
|
||||
<tr><td><tt class="docutils literal"><span class="pre">p</span></tt></td>
|
||||
<td>using the STLPort standard library rather than the default one supplied with
|
||||
your compiler.</td>
|
||||
</tr>
|
||||
<tr><td><tt class="docutils literal"><span class="pre">n</span></tt></td>
|
||||
<td>using STLPort's deprecated “native iostreams” feature.<a class="footnote-reference" href="#native" id="id20" name="id20"><sup>8</sup></a></td>
|
||||
<td>using STLPort's deprecated “native iostreams” feature.<a class="footnote-reference" href="#native" id="id19" name="id19"><sup>8</sup></a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -715,22 +709,22 @@ replaced by underscores. For example, version 1.31.1 would be
|
||||
tagged as "-1_31_1".</dd>
|
||||
<dt><tt class="docutils literal"><span class="pre">.lib</span></tt></dt>
|
||||
<dd><em>Extension</em>: determined according to the operating system's usual
|
||||
convention. On most *nix platforms the extensions are <tt class="docutils literal"><span class="pre">.a</span></tt>
|
||||
and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared libraries,
|
||||
respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared library
|
||||
and—except for static libraries built by <tt class="docutils literal"><span class="pre">gcc</span></tt> toolset, whose
|
||||
names always end in <tt class="docutils literal"><span class="pre">.a``—</span> <span class="pre">``.lib</span></tt> indicates a static or import
|
||||
library. Where supported by *nix toolsets, a full version
|
||||
extension is added (e.g. ".so.1.34") and a symbolic link to the
|
||||
library file, named without the trailing version number, will
|
||||
also be created.</dd>
|
||||
convention. On most unix-style platforms the extensions are
|
||||
<tt class="docutils literal"><span class="pre">.a</span></tt> and <tt class="docutils literal"><span class="pre">.so</span></tt> for static libraries (archives) and shared
|
||||
libraries, respectively. On Windows, <tt class="docutils literal"><span class="pre">.dll</span></tt> indicates a shared
|
||||
library and (except for static libraries built by the <tt class="docutils literal"><span class="pre">gcc</span></tt>
|
||||
toolset, whose names always end in <tt class="docutils literal"><span class="pre">.a</span></tt>) <tt class="docutils literal"><span class="pre">.lib</span></tt> indicates a
|
||||
static or import library. Where supported by toolsets on unix
|
||||
variants, a full version extension is added (e.g. ".so.1.34") and
|
||||
a symbolic link to the library file, named without the trailing
|
||||
version number, will also be created.</dd>
|
||||
</dl>
|
||||
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
|
||||
<!-- Software License, Version 1.0. (See accompanying -->
|
||||
<!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a class="toc-backref" href="#id42" id="test-your-program" name="test-your-program">6.4 Test Your Program</a></h2>
|
||||
<h2><a class="toc-backref" href="#id41" id="test-your-program" name="test-your-program">6.4 Test Your Program</a></h2>
|
||||
<p>To test our subject extraction, we'll filter the following text
|
||||
file. Copy it out of your browser and save it as <tt class="docutils literal"><span class="pre">jayne.txt</span></tt>:</p>
|
||||
<pre class="literal-block">
|
||||
@ -752,7 +746,7 @@ Spoil Rock Hunter?”</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a class="toc-backref" href="#id43" id="conclusion-and-further-resources" name="conclusion-and-further-resources">7 Conclusion and Further Resources</a></h1>
|
||||
<h1><a class="toc-backref" href="#id42" id="conclusion-and-further-resources" name="conclusion-and-further-resources">7 Conclusion and Further Resources</a></h1>
|
||||
<p>This concludes your introduction to Boost and to integrating it
|
||||
with your programs. As you start using Boost in earnest, there are
|
||||
surely a few additional points you'll wish we had covered. One day
|
||||
@ -832,7 +826,7 @@ have any source code mechanism for suppressing warnings.</td></tr>
|
||||
<table class="docutils footnote" frame="void" id="distinct" rules="none">
|
||||
<colgroup><col class="label" /><col /></colgroup>
|
||||
<tbody valign="top">
|
||||
<tr><td class="label"><a class="fn-backref" href="#id18" name="distinct">[6]</a></td><td>This convention distinguishes the static version of
|
||||
<tr><td class="label"><a class="fn-backref" href="#id17" name="distinct">[6]</a></td><td>This convention distinguishes the static version of
|
||||
a Boost library from the import library for an
|
||||
identically-configured Boost DLL, which would otherwise have the
|
||||
same name.</td></tr>
|
||||
@ -841,7 +835,7 @@ same name.</td></tr>
|
||||
<table class="docutils footnote" frame="void" id="debug-abi" rules="none">
|
||||
<colgroup><col class="label" /><col /></colgroup>
|
||||
<tbody valign="top">
|
||||
<tr><td class="label"><a class="fn-backref" href="#id19" name="debug-abi">[7]</a></td><td>These libraries were compiled without optimization
|
||||
<tr><td class="label"><a class="fn-backref" href="#id18" name="debug-abi">[7]</a></td><td>These libraries were compiled without optimization
|
||||
or inlining, with full debug symbols enabled, and without
|
||||
<tt class="docutils literal"><span class="pre">NDEBUG</span></tt> <tt class="docutils literal"><span class="pre">#define</span></tt>d. All though it's true that sometimes
|
||||
these choices don't affect binary compatibility with other
|
||||
@ -851,7 +845,7 @@ compiled code, you can't count on that with Boost libraries.</td></tr>
|
||||
<table class="docutils footnote" frame="void" id="native" rules="none">
|
||||
<colgroup><col class="label" /><col /></colgroup>
|
||||
<tbody valign="top">
|
||||
<tr><td class="label"><a class="fn-backref" href="#id20" name="native">[8]</a></td><td>This feature of STLPort is deprecated because it's
|
||||
<tr><td class="label"><a class="fn-backref" href="#id19" name="native">[8]</a></td><td>This feature of STLPort is deprecated because it's
|
||||
impossible to make it work transparently to the user; we don't
|
||||
recommend it.</td></tr>
|
||||
</tbody>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user