From 2c6a29d01bc969dbc8787f7ac944fc913ce68bcc Mon Sep 17 00:00:00 2001 From: Daniel James Date: Tue, 4 Apr 2017 23:25:39 +0100 Subject: Try to fix the python links in the getting started guide --- more/getting_started/detail/header-only.rst | 2 +- more/getting_started/detail/library-naming.rst | 2 +- more/getting_started/detail/links.rst | 2 +- more/getting_started/index.html | 4 ++-- more/getting_started/unix-variants.html | 20 ++++++++++---------- more/getting_started/windows.html | 26 +++++++++++++------------- 6 files changed, 28 insertions(+), 28 deletions(-) (limited to 'more') 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/index.html b/more/getting_started/index.html index 90db3cbda6..73a8597470 100644 --- a/more/getting_started/index.html +++ b/more/getting_started/index.html @@ -3,7 +3,7 @@ - + Boost Getting Started @@ -14,7 +14,7 @@ -
+

Use the latest version of this Getting Started guide

The Boost website version of this Getting Started guide may have updated information, such as the location of additional installers diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html index 73a4f1e069..c7a145a71d 100644 --- a/more/getting_started/unix-variants.html +++ b/more/getting_started/unix-variants.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Unix Variants @@ -72,7 +72,7 @@ tar --bzip2 -xf /path/to/boost_1_64_0 -

+

Other Packages

RedHat, Debian, and other distribution packagers supply Boost library packages, however you may need to adapt these @@ -123,7 +123,7 @@ the Python library's def.hpp header in

  • Some libraries have an “aggregate header” in boost/ that #includes all of the library's other headers. For -example, Boost.Python's aggregate header is

    +example, Boost.Python's aggregate header is

     boost/python.hpp.
    @@ -169,7 +169,7 @@ contains a subset of the Boost documentation. Start with

    3   Header-Only Libraries

    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.

    -
    +

    Nothing to Build?

    Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and @@ -188,7 +188,7 @@ treatment when linking.

  • Boost.Log (see build documentation)
  • Boost.MPI
  • Boost.ProgramOptions
    • -
  • Boost.Python (see the Boost.Python build documentation +
  • Boost.Python (see the Boost.Python build documentation before building and installing it)
  • Boost.Regex
  • Boost.Serialization
    • @@ -328,7 +328,7 @@ the directory where you want Boost.Build to be installed

    First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).

    -
    +

    Note

    If you previously chose a toolset for the purposes of building b2, you should assume it won't work and instead @@ -437,7 +437,7 @@ $ b2 --build-dir=/tmp/build-boost toolset=gcc library binaries in the stage/lib/ subdirectory of the Boost tree. To use a different directory pass the --stagedir=directory option to b2.

    -
    +

    Note

    b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.

    @@ -455,7 +455,7 @@ be interested in:

  • choosing a specific build variant by adding release or debug to the command line.
    • -
    +

    Note

    Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure @@ -618,7 +618,7 @@ libraries. runtime-debugging=on y -using a special debug build of Python. +using a special debug build of Python. python-debugging=on d @@ -715,7 +715,7 @@ mailing list.

  • Boost.Build mailing list
  • Index of all Boost library documentation
    • -
    +

    Onward

    Good luck, and have fun!

    diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html index 341bf6292d..c26ade2c51 100644 --- a/more/getting_started/windows.html +++ b/more/getting_started/windows.html @@ -3,7 +3,7 @@ - + Boost Getting Started on Windows @@ -14,7 +14,7 @@ -
    +

    A note to Cygwin and MinGW users

    If you plan to use your tools from the Windows command prompt, you're in the right place. If you plan to build from the Cygwin @@ -103,7 +103,7 @@ the Python library's def.hpp header in

  • Some libraries have an “aggregate header” in boost\ that #includes all of the library's other headers. For -example, Boost.Python's aggregate header is

    +example, Boost.Python's aggregate header is

     boost\python.hpp.
    @@ -154,7 +154,7 @@ contains a subset of the Boost documentation. Start with

    3   Header-Only Libraries

    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.

    -
    +

    Nothing to Build?

    Most Boost libraries are header-only: they consist entirely of header files containing templates and inline functions, and @@ -173,7 +173,7 @@ treatment when linking.

  • Boost.Log (see build documentation)
  • Boost.MPI
  • Boost.ProgramOptions
    • -
  • Boost.Python (see the Boost.Python build documentation +
  • Boost.Python (see the Boost.Python build documentation before building and installing it)
  • Boost.Regex
  • Boost.Serialization
    • @@ -228,7 +228,7 @@ int main() }

    Copy the text of this program into a file called example.cpp.

    -
    +

    Note

    To build the examples in this guide, you can use an Integrated Development Environment (IDE) like Visual Studio, or @@ -387,7 +387,7 @@ the directory where you want Boost.Build to be installed

    First, find the toolset corresponding to your compiler in the following table (an up-to-date list is always available in the Boost.Build documentation).

    -
    +

    Note

    If you previously chose a toolset for the purposes of building b2, you should assume it won't work and instead @@ -506,7 +506,7 @@ list.

    library binaries in the stage\lib\ subdirectory of the Boost tree. To use a different directory pass the --stagedir=directory option to b2.

    -
    +

    Note

    b2 is case-sensitive; it is important that all the parts shown in bold type above be entirely lower-case.

    @@ -524,7 +524,7 @@ be interested in:

  • choosing a specific build variant by adding release or debug to the command line.
    • -
    +

    Note

    Boost.Build can produce a great deal of output, which can make it easy to miss problems. If you want to make sure @@ -607,7 +607,7 @@ build settings. whose compile configuration is compatible with the rest of your project. -

    +

    Auto-Linking

    Most Windows compilers and linkers have so-called “auto-linking support,” which eliminates the second challenge. Special code in @@ -646,7 +646,7 @@ cl /EHsc /I path\to\boost_1_64_0 exam

    6.3   Library Naming

    -
    +

    Note

    If, like Visual C++, your compiler supports auto-linking, you can probably skip to the next step.

    @@ -706,7 +706,7 @@ libraries. runtime-debugging=on y -using a special debug build of Python. +using a special debug build of Python. python-debugging=on d @@ -785,7 +785,7 @@ mailing list.

  • Boost.Build mailing list
  • Index of all Boost library documentation
    • -
    +

    Onward

    Good luck, and have fun!

    -- cgit v1.2.1