Doc and build fixes by Dave Abrahams.

thwitt · thwitt · commit 28513257485f · 2007-07-06T19:47:17.000Z
[SVN r38154]
diff --git a/doc/building.html b/doc/building.html
@@ -75,7 +75,7 @@ <h1><a class="toc-backref" href="#id26">2&nbsp;&nbsp;&nbsp;Background</a></h1>
 modules or the executable containing <tt class="docutils literal"><span class="pre">main()</span></tt>.</p>
 </div>
 <div class="section" id="no-install-quickstart">
-<h1><a class="toc-backref" href="#id27">3&nbsp;&nbsp;&nbsp;No-Install Quickstart</a></h1>
+<span id="quickstart"></span><h1><a class="toc-backref" href="#id27">3&nbsp;&nbsp;&nbsp;No-Install Quickstart</a></h1>
 <p>There is no need to “install Boost” in order to get started using
 Boost.Python.  These instructions use <a class="reference external" href="../../../tools/build/index.html">Boost.Build</a> projects,
 which will build those binaries as soon as they're needed.  Your
@@ -273,14 +273,6 @@ <h1><a class="toc-backref" href="#id32">4&nbsp;&nbsp;&nbsp;Installing Boost.Pyth
 argument to <tt class="docutils literal"><span class="pre">bjam</span></tt> (or the <tt class="docutils literal"><span class="pre">--with-libraries=python</span></tt> argument
 to <tt class="docutils literal"><span class="pre">configure</span></tt>), so only the Boost.Python binary will be built,
 rather than all the Boost binaries.</p>
-<div class="admonition-windows-users-no-auto-link-support admonition">
-<p class="first admonition-title">Windows Users: No Auto-Link Support</p>
-<p class="last">Boost.Python does not yet support the <a class="reference external" href="../../../more/getting_started/windows.html#link-your-program-to-a-boost-library">auto-link</a> feature, so if
-you're not using the <a class="reference internal" href="#no-install-quickstart">quickstart</a> method, you'll have to pay
-attention to the names of generated libraries and add extra link
-arguments not shown in the <a class="reference external" href="../../../more/getting_started/index.html">Getting Started Guide</a> to select the
-right library.</p>
-</div>
 </div>
 <div class="section" id="configuring-boost-build">
 <h1><a class="toc-backref" href="#id33">5&nbsp;&nbsp;&nbsp;Configuring Boost.Build</a></h1>
@@ -309,7 +301,7 @@ <h1><a class="toc-backref" href="#id33">5&nbsp;&nbsp;&nbsp;Configuring Boost.Bui
 </pre>
 <p>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 <a class="reference internal" href="#no-install-quickstart">quickstart</a>
+(e.g. when referred to by another project as in the <a class="reference internal" href="#quickstart">quickstart</a>
 method).  If instead you are linking against separately-compiled
 Boost.Python binaries, you should set up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file
 with at least the minimal incantation above.</p>
@@ -570,9 +562,6 @@ <h1><a class="toc-backref" href="#id42">10&nbsp;&nbsp;&nbsp;Notes for MinGW (and
 <li><a class="reference external" href="../../../more/getting_started/windows.html#library-naming">on Windows</a></li>
 <li><a class="reference external" href="../../../more/getting_started/unix-variants.html#library-naming">on Unix variants</a></li>
 </ul>
-<p class="last">Be sure to read this section even if your compiler supports
-auto-linking, as Boost.Python does not yet take advantage of
-that feature.</p>
 </td></tr>
 </tbody>
 </table>
@@ -639,7 +628,7 @@ <h1><a class="toc-backref" href="#id42">10&nbsp;&nbsp;&nbsp;Notes for MinGW (and
 <div class="footer">
 <hr class="footer" />
 <a class="reference external" href="./building.rst">View document source</a>.
-Generated on: 2007-05-07 18:58 UTC.
+Generated on: 2007-07-02 13:46 UTC.
 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
 
 </div>
diff --git 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
@@ -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 ;
+
