diff options
Diffstat (limited to 'more')
| -rw-r--r-- | more/getting_started/detail/header-only.rst | 2 | ||||
| -rw-r--r-- | more/getting_started/detail/library-naming.rst | 2 | ||||
| -rw-r--r-- | more/getting_started/detail/links.rst | 2 | ||||
| -rw-r--r-- | more/getting_started/detail/release-variables.rst | 8 | ||||
| -rw-r--r-- | more/getting_started/unix-variants.html | 28 | ||||
| -rw-r--r-- | more/getting_started/windows.html | 32 |
6 files changed, 37 insertions, 37 deletions
diff --git a/more/getting_started/detail/header-only.rst b/more/getting_started/detail/header-only.rst index 5dd0a019b6..db0056a7e8 100644 --- a/more/getting_started/detail/header-only.rst +++ b/more/getting_started/detail/header-only.rst @@ -39,7 +39,7 @@ The only Boost libraries that *must* be built separately are: * Boost.Wave_ __ ../../libs/log/doc/html/log/installation/config.html -__ ../../libs/python/doc/building.html +__ ../../libs/python/doc/html/building.html A few libraries have optional separately-compiled binaries: diff --git a/more/getting_started/detail/library-naming.rst b/more/getting_started/detail/library-naming.rst index a92f3ddc4a..08da85f071 100644 --- a/more/getting_started/detail/library-naming.rst +++ b/more/getting_started/detail/library-naming.rst @@ -73,5 +73,5 @@ following elements: .. .. _Boost.Build toolset names: toolset-name_ -__ ../../libs/python/doc/building.html#python-debugging-builds +__ ../../libs/python/doc/html/building/python_debugging_builds.html diff --git a/more/getting_started/detail/links.rst b/more/getting_started/detail/links.rst index 1a6d9b7495..fb3109cb1f 100644 --- a/more/getting_started/detail/links.rst +++ b/more/getting_started/detail/links.rst @@ -15,7 +15,7 @@ .. _Boost.Math: ../../libs/math/index.html .. _Boost.MPI: ../../libs/mpi/index.html .. _Boost.ProgramOptions: ../../libs/program_options/index.html -.. _Boost.Python: ../../libs/python/doc/building.html +.. _Boost.Python: ../../libs/python/doc/html/building.html .. _Boost.Random: ../../libs/random/index.html .. _Boost.Regex: ../../libs/regex/index.html .. _Boost.Serialization: ../../libs/serialization/index.html diff --git a/more/getting_started/detail/release-variables.rst b/more/getting_started/detail/release-variables.rst index 9c2c78aff2..250986abfa 100644 --- a/more/getting_started/detail/release-variables.rst +++ b/more/getting_started/detail/release-variables.rst @@ -5,8 +5,8 @@ .. This file contains all the definitions that need to be updated .. for each new release of Boost. -.. |boost-version-number| replace:: 1.63.0 -.. |boost_ver| replace:: ``boost_1_63_0`` -.. |boost_ver-bold| replace:: **boost_1_63_0** +.. |boost-version-number| replace:: 64 +.. |boost_ver| replace:: ``boost_1_64_0`` +.. |boost_ver-bold| replace:: **boost_1_64_0** -.. _sf-download: http://www.boost.org/users/history/version_1_63_0.html +.. _sf-download: http://www.boost.org/users/history/version_1_64_0.html diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index fedb53fd2d..c7a145a71d 100644 --- a/more/getting_started/unix-variants.html +++ b/more/getting_started/unix-variants.html @@ -61,14 +61,14 @@ <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_63_0.html">SourceForge</a>:</p> +distribution from <a class="reference external" href="http://www.boost.org/users/history/version_1_64_0.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_63_0.html"><tt class="docutils literal">boost_1_63_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_64_0.html"><tt class="docutils literal">boost_1_64_0</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_63_0</tt>.tar.bz2 +tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_64_0</tt>.tar.bz2 </pre> </li> </ol> @@ -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_63_0.html">SourceForge</a>.</p> +from <a class="reference external" href="http://www.boost.org/users/history/version_1_64_0.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_63_0</strong><strong>/</strong> .................<em>The “boost root directory”</em> +<strong>boost_1_64_0</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> @@ -123,7 +123,7 @@ the Python library's <tt class="docutils literal">def.hpp</tt> header in</p> </li> <li><p class="first">Some libraries have an “aggregate header” in <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt> that <tt class="docutils literal">#include</tt>s all of the library's other headers. For -example, <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p> +example, <a class="reference external" href="../../libs/python/doc/html/building.html">Boost.Python</a>'s aggregate header is</p> <pre class="literal-block"> <tt class="docutils literal">boost</tt><tt class="docutils literal">/</tt><tt class="docutils literal">python.hpp</tt>. </pre> @@ -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_63_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_64_0</tt>) is sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and mailing lists .</p> </li> @@ -188,7 +188,7 @@ treatment when linking.</p> <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> <li><a class="reference external" href="../../libs/mpi/index.html">Boost.MPI</a></li> <li><a class="reference external" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li> -<li><a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a> (see the <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python build documentation</a> +<li><a class="reference external" href="../../libs/python/doc/html/building.html">Boost.Python</a> (see the <a class="reference external" href="../../libs/python/doc/html/building.html">Boost.Python build documentation</a> before building and installing it)</li> <li><a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a></li> <li><a class="reference external" href="../../libs/serialization/index.html">Boost.Serialization</a></li> @@ -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_63_0</tt> example.cpp -o example +c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_64_0</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_63_0</tt> +<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_64_0</tt> <strong>$</strong> ./bootstrap.sh --help </pre> <p>Select your configuration options and invoke <tt class="docutils literal">./bootstrap.sh</tt> again @@ -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_63_0</tt> +$ cd ~/<tt class="docutils literal">boost_1_64_0</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> @@ -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_63_0</tt> example.cpp -o example <strong>\</strong> +$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_64_0</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_63_0</tt> example.cpp -o example <strong>\</strong> +$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_64_0</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 @@ -618,7 +618,7 @@ libraries.</td> <td>runtime-debugging=on</td> </tr> <tr><td><tt class="docutils literal">y</tt></td> -<td>using a special <a class="reference external" href="../../libs/python/doc/building.html#python-debugging-builds">debug build of Python</a>.</td> +<td>using a special <a class="reference external" href="../../libs/python/doc/html/building/python_debugging_builds.html">debug build of Python</a>.</td> <td>python-debugging=on</td> </tr> <tr><td><tt class="docutils literal">d</tt></td> diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html index 5c1f5b8ecb..c26ade2c51 100644 --- a/more/getting_started/windows.html +++ b/more/getting_started/windows.html @@ -61,7 +61,7 @@ not supported—they may or may not work.</p> <div class="section" id="get-boost"> <h1><a class="toc-backref" href="#id28">1 Get Boost</a></h1> <p>The most reliable way to get a copy of Boost is to -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 +download <a class="reference external" href="http://www.boost.org/users/history/version_1_64_0.html"><tt class="docutils literal">boost_1_64_0</tt><tt class="docutils literal">.7z</tt></a> or <a class="reference external" href="http://www.boost.org/users/history/version_1_64_0.html"><tt class="docutils literal">boost_1_64_0</tt><tt class="docutils literal">.zip</tt></a> and unpack it to install a complete Boost distribution.<a class="footnote-reference" href="#zip" id="id2"><sup>1</sup></a></p> <!-- Copyright David Abrahams 2006. Distributed under the Boost --> <!-- Software License, Version 1.0. (See accompanying --> @@ -71,7 +71,7 @@ distribution.<a class="footnote-reference" href="#zip" id="id2"><sup>1</sup></a> <h1><a class="toc-backref" href="#id29">2 The Boost Distribution</a></h1> <p>This is a sketch of the resulting directory structure:</p> <pre class="literal-block"> -<strong>boost_1_63_0</strong><strong>\</strong> .................<em>The “boost root directory”</em> +<strong>boost_1_64_0</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> <strong>lib</strong><strong>\</strong> .....................<em>precompiled library binaries</em> @@ -103,7 +103,7 @@ the Python library's <tt class="docutils literal">def.hpp</tt> header in</p> </li> <li><p class="first">Some libraries have an “aggregate header” in <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt> that <tt class="docutils literal">#include</tt>s all of the library's other headers. For -example, <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a>'s aggregate header is</p> +example, <a class="reference external" href="../../libs/python/doc/html/building.html">Boost.Python</a>'s aggregate header is</p> <pre class="literal-block"> <tt class="docutils literal">boost</tt><tt class="docutils literal">\</tt><tt class="docutils literal">python.hpp</tt>. </pre> @@ -116,7 +116,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"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt>) is +<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_64_0</tt>) is sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and mailing lists .</p> </li> @@ -173,7 +173,7 @@ treatment when linking.</p> <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> <li><a class="reference external" href="../../libs/mpi/index.html">Boost.MPI</a></li> <li><a class="reference external" href="../../libs/program_options/index.html">Boost.ProgramOptions</a></li> -<li><a class="reference external" href="../../libs/python/doc/building.html">Boost.Python</a> (see the <a class="reference external" href="../../libs/python/doc/building.html">Boost.Python build documentation</a> +<li><a class="reference external" href="../../libs/python/doc/html/building.html">Boost.Python</a> (see the <a class="reference external" href="../../libs/python/doc/html/building.html">Boost.Python build documentation</a> before building and installing it)</li> <li><a class="reference external" href="../../libs/regex/index.html">Boost.Regex</a></li> <li><a class="reference external" href="../../libs/serialization/index.html">Boost.Serialization</a></li> @@ -256,7 +256,7 @@ cd <em>path</em>\<em>to</em>\<em>some</em>\<em>directory</em> </pre> <p>followed by Return. For example,</p> <pre class="literal-block"> -cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt> +cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_64_0</tt> </pre> <p class="last">Long commands can be continued across several lines by typing a caret (<tt class="docutils literal">^</tt>) at the end of all but the last line. Some examples @@ -281,7 +281,7 @@ select <em>Properties</em> from the resulting pop-up menu</p> <li><p class="first">In <em>Configuration Properties</em> > <em>C/C++</em> > <em>General</em> > <em>Additional Include Directories</em>, enter the path to the Boost root directory, for example</p> <blockquote> -<p><tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt></p> +<p><tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_64_0</tt></p> </blockquote> </li> <li><p class="first">In <em>Configuration Properties</em> > <em>C/C++</em> > <em>Precompiled Headers</em>, change @@ -319,7 +319,7 @@ Visual Studio compiler. In that window, set the <a class="reference internal" h directory</a> to a suitable location for creating some temporary files and type the following command followed by the Return key:</p> <pre class="literal-block"> -cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_63_0</tt> <em>path</em>\<em>to</em>\example.cpp +cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_64_0</tt> <em>path</em>\<em>to</em>\example.cpp </pre> <p>To test the result, type:</p> <pre class="literal-block"> @@ -488,8 +488,8 @@ b2 <strong>--build-dir=</strong><a class="reference internal" href="#id13"><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:<a class="footnote-reference" href="#continuation" id="id15"><sup>3</sup></a></p> <pre class="literal-block"> -C:\WINDOWS> cd <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"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_63_0</tt>> b2 <strong>^</strong> +C:\WINDOWS> cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_64_0</tt> +<tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_64_0</tt>> b2 <strong>^</strong> More? <strong>--build-dir=</strong>"C:\Documents and Settings\dave\build-boost" <strong>^</strong> More? <strong>--build-type=complete</strong> <strong>msvc</strong> stage </pre> @@ -628,7 +628,7 @@ earlier:</p> select <em>Properties</em> from the resulting pop-up menu</li> <li>In <em>Configuration Properties</em> > <em>Linker</em> > <em>Additional Library Directories</em>, enter the path to the Boost binaries, -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> +e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_64_0</tt><tt class="docutils literal">\lib\</tt>.</li> <li>From the <em>Build</em> menu, select <em>Build Solution</em>.</li> </ol> <p><a class="reference internal" href="#test-your-program"><em>skip to the next step</em></a></p> @@ -638,10 +638,10 @@ e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boos <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 -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> +in <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_64_0</tt><tt class="docutils literal">\lib</tt>:</p> <pre class="literal-block"> -cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_63_0</tt> example.cpp <strong>^</strong> - <strong>/link /LIBPATH:</strong><strong>C:\Program Files\boost\</strong><strong>boost_1_63_0</strong><strong>\lib</strong> +cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_64_0</tt> example.cpp <strong>^</strong> + <strong>/link /LIBPATH:</strong><strong>C:\Program Files\boost\</strong><strong>boost_1_64_0</strong><strong>\lib</strong> </pre> </div> <div class="section" id="library-naming"> @@ -706,7 +706,7 @@ libraries.</td> <td>runtime-debugging=on</td> </tr> <tr><td><tt class="docutils literal">y</tt></td> -<td>using a special <a class="reference external" href="../../libs/python/doc/building.html#python-debugging-builds">debug build of Python</a>.</td> +<td>using a special <a class="reference external" href="../../libs/python/doc/html/building/python_debugging_builds.html">debug build of Python</a>.</td> <td>python-debugging=on</td> </tr> <tr><td><tt class="docutils literal">d</tt></td> @@ -797,7 +797,7 @@ mailing list</a>.</p> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> <tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>We recommend -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 +downloading <a class="reference external" href="http://www.boost.org/users/history/version_1_64_0.html"><tt class="docutils literal">boost_1_64_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 it. We no longer recommend .zip files for Boost because they are twice as large as the equivalent .7z files. We don't recommend using Windows' built-in decompression as it can be painfully slow for large archives.</td></tr> |