diff options
author | Daniel James <daniel@calamity.org.uk> | 2017-08-28 00:00:41 +0100 |
---|---|---|
committer | Daniel James <daniel@calamity.org.uk> | 2017-08-28 00:00:41 +0100 |
commit | 13cc3507fbcc12a95654b23a1a1b521837deeb48 (patch) | |
tree | 07bf795356b1ba8c01ab6893b86d2645e4189f0e /more/getting_started/unix-variants.html | |
parent | 23b96b68bd697ecafb1c8dccf918b563f2628a72 (diff) | |
download | boost-13cc3507fbcc12a95654b23a1a1b521837deeb48.tar.gz |
Kick off 1.65.1
Diffstat (limited to 'more/getting_started/unix-variants.html')
-rw-r--r-- | more/getting_started/unix-variants.html | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index e134805c4a..82b2a27530 100644 --- a/more/getting_started/unix-variants.html +++ b/more/getting_started/unix-variants.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="generator" content="Docutils 0.13.1: http://docutils.sourceforge.net/" /> +<meta name="generator" content="Docutils 0.12: http://docutils.sourceforge.net/" /> <title>Boost Getting Started on Unix Variants</title> <meta content="Getting Started with Boost on Unix Variants (including Linux and MacOS)" name="description" /> <link rel="stylesheet" href="../../rst.css" type="text/css" /> @@ -61,18 +61,18 @@ <div class="section" id="get-boost"> <h1><a class="toc-backref" href="#id20">1 Get Boost</a></h1> <p>The most reliable way to get a copy of Boost is to download a -distribution from <a class="reference external" href="http://www.boost.org/users/history/version_1_65_0.html">SourceForge</a>:</p> +distribution from <a class="reference external" href="http://www.boost.org/users/history/version_1_65_1.html">SourceForge</a>:</p> <ol class="arabic"> -<li><p class="first">Download <a class="reference external" href="http://www.boost.org/users/history/version_1_65_0.html"><tt class="docutils literal">boost_1_65_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p> +<li><p class="first">Download <a class="reference external" href="http://www.boost.org/users/history/version_1_65_1.html"><tt class="docutils literal">boost_1_65_1</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p> </li> <li><p class="first">In the directory where you want to put the Boost installation, execute</p> <pre class="literal-block"> -tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_65_0</tt>.tar.bz2 +tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_65_1</tt>.tar.bz2 </pre> </li> </ol> -<div class="admonition admonition-other-packages"> +<div class="admonition-other-packages admonition"> <p class="first admonition-title">Other Packages</p> <p class="last">RedHat, Debian, and other distribution packagers supply Boost library packages, however you may need to adapt these @@ -81,7 +81,7 @@ creators usually choose to break Boost up into several packages, reorganize the directory structure of the Boost distribution, and/or rename the library binaries.<a class="footnote-reference" href="#packagers" id="id2"><sup>1</sup></a> If you have any trouble, we suggest using an official Boost distribution -from <a class="reference external" href="http://www.boost.org/users/history/version_1_65_0.html">SourceForge</a>.</p> +from <a class="reference external" href="http://www.boost.org/users/history/version_1_65_1.html">SourceForge</a>.</p> </div> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> @@ -91,7 +91,7 @@ from <a class="reference external" href="http://www.boost.org/users/history/vers <h1><a class="toc-backref" href="#id21">2 The Boost Distribution</a></h1> <p>This is a sketch of the resulting directory structure:</p> <pre class="literal-block"> -<strong>boost_1_65_0</strong><strong>/</strong> .................<em>The “boost root directory”</em> +<strong>boost_1_65_1</strong><strong>/</strong> .................<em>The “boost root directory”</em> <strong>index.htm</strong> .........<em>A copy of www.boost.org starts here</em> <strong>boost</strong><strong>/</strong> .........................<em>All Boost Header files</em> <tt class="docutils literal"> </tt> @@ -136,7 +136,7 @@ anything you can use in these directories.</p> </div> <p>It's important to note the following:</p> <ol class="arabic" id="boost-root-directory"> -<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_65_0</tt>) is +<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_65_1</tt>) is sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and mailing lists .</p> </li> @@ -169,7 +169,7 @@ contains a subset of the Boost documentation. Start with <h1><a class="toc-backref" href="#id22">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 admonition-nothing-to-build"> +<div class="admonition-nothing-to-build admonition"> <p class="first admonition-title">Nothing to Build?</p> <p class="last">Most Boost libraries are <strong>header-only</strong>: they consist <em>entirely of header files</em> containing templates and inline functions, and @@ -246,7 +246,7 @@ int main() <p>Now, in the directory where you saved <tt class="docutils literal">example.cpp</tt>, issue the following command:</p> <pre class="literal-block"> -c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_65_0</tt> example.cpp -o example +c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_65_1</tt> example.cpp -o example </pre> <p>To test the result, type:</p> <pre class="literal-block"> @@ -277,7 +277,7 @@ you'll need to acquire library binaries.</p> <p>Issue the following commands in the shell (don't type <tt class="docutils literal">$</tt>; that represents the shell's prompt):</p> <pre class="literal-block"> -<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_65_0</tt> +<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_65_1</tt> <strong>$</strong> ./bootstrap.sh --help </pre> <p>Select your configuration options and invoke <tt class="docutils literal">./bootstrap.sh</tt> again @@ -328,7 +328,7 @@ the directory where you want Boost.Build to be installed</li> <p>First, find the toolset corresponding to your compiler in the 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 Boost.Build documentation</a>).</p> -<div class="admonition note"> +<div class="note"> <p class="first admonition-title">Note</p> <p class="last">If you previously chose a toolset for the purposes of <a class="reference external" href="../../doc/html/bbv2/installation.html">building b2</a>, you should assume it won't work and instead @@ -426,7 +426,7 @@ b2 <strong>--build-dir=</strong><a class="reference internal" href="#id11"><em>b please see the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a>.</p> <p>For example, your session might look like this:</p> <pre class="literal-block"> -$ cd ~/<tt class="docutils literal">boost_1_65_0</tt> +$ cd ~/<tt class="docutils literal">boost_1_65_1</tt> $ b2 <strong>--build-dir=</strong>/tmp/build-boost <strong>toolset=</strong>gcc stage </pre> <p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>”.</p> @@ -437,7 +437,7 @@ $ b2 <strong>--build-dir=</strong>/tmp/build-boost <strong>toolset=</strong>gcc 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 the Boost tree. To use a different directory pass the <tt class="docutils literal"><span class="pre">--stagedir=</span></tt><em>directory</em> option to <tt class="docutils literal">b2</tt>.</p> -<div class="admonition note"> +<div class="note"> <p class="first admonition-title">Note</p> <p class="last"><tt class="docutils literal">b2</tt> is case-sensitive; it is important that all the parts shown in <strong>bold</strong> type above be entirely lower-case.</p> @@ -455,7 +455,7 @@ be interested in:</p> <li>choosing a specific build variant by adding <tt class="docutils literal">release</tt> or <tt class="docutils literal">debug</tt> to the command line.</li> </ul> -<div class="admonition note"> +<div class="note"> <p class="first admonition-title">Note</p> <p class="last">Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure @@ -542,14 +542,14 @@ project.</li> <ol class="upperalpha"> <li><p class="first">You can specify the full path to each library:</p> <pre class="literal-block"> -$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_65_0</tt> example.cpp -o example <strong>\</strong> +$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_65_1</tt> example.cpp -o example <strong>\</strong> <strong>~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a</strong> </pre> </li> <li><p class="first">You can separately specify a directory to search (with <tt class="docutils literal"><span class="pre">-L</span></tt><em>directory</em>) and a library name to search for (with <tt class="docutils literal"><span class="pre">-l</span></tt><em>library</em>,<a class="footnote-reference" href="#lowercase-l" id="id15"><sup>2</sup></a> dropping the filename's leading <tt class="docutils literal">lib</tt> and trailing suffix (<tt class="docutils literal">.a</tt> in this case):</p> <pre class="literal-block"> -$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_65_0</tt> example.cpp -o example <strong>\</strong> +$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_65_1</tt> example.cpp -o example <strong>\</strong> <strong>-L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36</strong> </pre> <p>As you can see, this method is just as terse as method A for one @@ -715,7 +715,7 @@ mailing list</a>.</p> <li><a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a></li> <li><a class="reference external" href="../../libs/index.html">Index of all Boost library documentation</a></li> </ul> -<div class="admonition admonition-onward"> +<div class="admonition-onward admonition"> <p class="first admonition-title">Onward</p> <blockquote class="epigraph last"> <p>Good luck, and have fun!</p> |