There is no need to “install Boost” in order to get started using Boost.Python. These instructions use Boost.Build projects, which will build those binaries as soon as they're needed. Your @@ -273,14 +273,6 @@ from source, you might want to supply the bjam (or the --with-libraries=python argument to configure), so only the Boost.Python binary will be built, rather than all the Boost binaries.
-Windows Users: No Auto-Link Support
-Boost.Python does not yet support the auto-link feature, so if -you're not using the quickstart method, you'll have to pay -attention to the names of generated libraries and add extra link -arguments not shown in the Getting Started Guide to select the -right library.
-which automatically looks for Python in the most likely places. However, that only happens when using the Boost.Python project file -(e.g. when referred to by another project as in the quickstart +(e.g. when referred to by another project as in the quickstart method). If instead you are linking against separately-compiled Boost.Python binaries, you should set up a user-config.jam file with at least the minimal incantation above.
@@ -570,9 +562,6 @@ static and dynamic builds of Boost.Python:Be sure to read this section even if your compiler supports -auto-linking, as Boost.Python does not yet take advantage of -that feature.
@@ -639,7 +628,7 @@ You may also find diff --git a/doc/building.rst b/doc/building.rst index 6f4fd02a..d3a93800 100644 --- a/doc/building.rst +++ b/doc/building.rst @@ -65,6 +65,8 @@ dynamically-loaded libraries with a single entry point, which means you can change them without rebuilding either the other extension modules or the executable containing ``main()``. +.. _quickstart: + No-Install Quickstart ===================== @@ -326,17 +328,6 @@ argument to ``bjam`` (or the ``--with-libraries=python`` argument to ``configure``), so only the Boost.Python binary will be built, rather than all the Boost binaries. -.. Admonition:: Windows Users: No Auto-Link Support - - Boost.Python does not yet support the `auto-link`_ feature, so if - you're not using the quickstart_ method, you'll have to pay - attention to the names of generated libraries and add extra link - arguments not shown in the `Getting Started Guide`_ to select the - right library. - -.. _auto-link: ../../../more/getting_started/windows.html#link-your-program-to-a-boost-library - -.. _quickstart: `no-install quickstart`_ Configuring Boost.Build ======================= @@ -652,10 +643,6 @@ __ http://www.python.org/doc/current/inst/index.html __ ../../../more/getting_started/windows.html#library-naming __ ../../../more/getting_started/unix-variants.html#library-naming - Be sure to read this section even if your compiler supports - auto-linking, as Boost.Python does not yet take advantage of - that feature. - .. [#toolset-specific] Because of the way most \*nix platforms share symbols among dynamically-loaded objects, I'm not certain that extension modules built with different compiler toolsets diff --git a/example/quickstart/Jamroot b/example/quickstart/Jamroot index 72924a27..569dae13 100755 --- a/example/quickstart/Jamroot +++ b/example/quickstart/Jamroot @@ -35,3 +35,9 @@ testing.run embedding : # requirements : test_embed ; # name of test +# Create a "test" target that runs all the tests +alias test : test_ext test_embed ; + +# make sure the tests don't run by default +explicit test_ext test_embed test ; +