Update of /cvsroot/boost/boost/libs/python/doc
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv13377
Modified Files:
Tag: RC_1_34_0
building.rst building.html Jamfile
Log Message:
Jamfile had extra bogus tst executable target
Build/test instructions were outdated somehow; a checkin must've failed.
Index: building.rst
===================================================================
RCS file: /cvsroot/boost/boost/libs/python/doc/building.rst,v
retrieving revision 1.5.2.2
retrieving revision 1.5.2.3
diff -u -d -r1.5.2.2 -r1.5.2.3
--- building.rst 4 May 2007 00:56:22 -0000 1.5.2.2
+++ building.rst 7 May 2007 19:00:01 -0000 1.5.2.3
@@ -592,7 +592,7 @@
Since pre-built âpython debuggingâ versions of the Python
executable and libraries are not supplied with most distributions
-of Python, [#get-debug-build] and we didn't want to force our users
+of Python, [#get-debug-build]_ and we didn't want to force our users
to build them, Boost.Build does not automatically enable python
debugging in its ``debug`` build variant (which is the default).
Instead there is a special build property called
Index: building.html
===================================================================
RCS file: /cvsroot/boost/boost/libs/python/doc/building.html,v
retrieving revision 1.32.4.4
retrieving revision 1.32.4.5
diff -u -d -r1.32.4.4 -r1.32.4.5
--- building.html 4 May 2007 00:56:22 -0000 1.32.4.4
+++ building.html 7 May 2007 19:00:01 -0000 1.32.4.5
@@ -9,55 +9,55 @@
</head>
<body>
<div class="document" id="logo-boost-python-build-and-test-howto">
-<h1 class="title"><a class="reference" href="../index.htm"><img alt="Boost C++
Libraries:" class="boost-logo" src="../../../boost.png" /></a> Boost.Python
Build and Test HOWTO</h1>
+<h1 class="title"><a class="reference external" href="../index.htm"><img
alt="Boost C++ Libraries:" class="boost-logo" src="../../../boost.png" /></a>
Boost.Python Build and Test HOWTO</h1>
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
<!-- Software License, Version 1.0. (See accompanying -->
<!-- file LICENSE_1_0.txt or copy at -->
<!-- http://www.boost.org/LICENSE_1_0.txt) -->
-<div class="contents sidebar small topic">
-<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
+<div class="contents sidebar small topic" id="contents">
+<p class="topic-title first">Contents</p>
<ul class="auto-toc simple">
-<li><a class="reference" href="#requirements" id="id24"
name="id24">1 Requirements</a></li>
-<li><a class="reference" href="#background" id="id25"
name="id25">2 Background</a></li>
-<li><a class="reference" href="#no-install-quickstart" id="id26"
name="id26">3 No-Install Quickstart</a><ul class="auto-toc">
-<li><a class="reference" href="#basic-procedure" id="id27"
name="id27">3.1 Basic Procedure</a></li>
-<li><a class="reference" href="#in-case-of-trouble" id="id28"
name="id28">3.2 In Case of Trouble</a></li>
-<li><a class="reference" href="#in-case-everything-seemed-to-work" id="id29"
name="id29">3.3 In Case Everything Seemed to Work</a></li>
-<li><a class="reference" href="#modifying-the-example-project" id="id30"
name="id30">3.4 Modifying the Example Project</a></li>
+<li><a class="reference internal" href="#requirements"
id="id25">1 Requirements</a></li>
+<li><a class="reference internal" href="#background"
id="id26">2 Background</a></li>
+<li><a class="reference internal" href="#no-install-quickstart"
id="id27">3 No-Install Quickstart</a><ul class="auto-toc">
+<li><a class="reference internal" href="#basic-procedure"
id="id28">3.1 Basic Procedure</a></li>
+<li><a class="reference internal" href="#in-case-of-trouble"
id="id29">3.2 In Case of Trouble</a></li>
+<li><a class="reference internal" href="#in-case-everything-seemed-to-work"
id="id30">3.3 In Case Everything Seemed to Work</a></li>
+<li><a class="reference internal" href="#modifying-the-example-project"
id="id31">3.4 Modifying the Example Project</a></li>
</ul>
</li>
-<li><a class="reference" href="#installing-boost-python-on-your-system"
id="id31" name="id31">4 Installing Boost.Python on your
System</a></li>
-<li><a class="reference" href="#configuring-boost-build" id="id32"
name="id32">5 Configuring Boost.Build</a><ul class="auto-toc">
-<li><a class="reference" href="#python-configuration-parameters" id="id33"
name="id33">5.1 Python Configuration Parameters</a></li>
-<li><a class="reference" href="#examples" id="id34"
name="id34">5.2 Examples</a></li>
+<li><a class="reference internal"
href="#installing-boost-python-on-your-system"
id="id32">4 Installing Boost.Python on your System</a></li>
+<li><a class="reference internal" href="#configuring-boost-build"
id="id33">5 Configuring Boost.Build</a><ul class="auto-toc">
+<li><a class="reference internal" href="#python-configuration-parameters"
id="id34">5.1 Python Configuration Parameters</a></li>
+<li><a class="reference internal" href="#examples"
id="id35">5.2 Examples</a></li>
</ul>
</li>
-<li><a class="reference" href="#choosing-a-boost-python-library-binary"
id="id35" name="id35">6 Choosing a Boost.Python Library
Binary</a><ul class="auto-toc">
-<li><a class="reference" href="#the-dynamic-binary" id="id36"
name="id36">6.1 The Dynamic Binary</a></li>
-<li><a class="reference" href="#the-static-binary" id="id37"
name="id37">6.2 The Static Binary</a></li>
+<li><a class="reference internal"
href="#choosing-a-boost-python-library-binary"
id="id36">6 Choosing a Boost.Python Library Binary</a><ul
class="auto-toc">
+<li><a class="reference internal" href="#the-dynamic-binary"
id="id37">6.1 The Dynamic Binary</a></li>
+<li><a class="reference internal" href="#the-static-binary"
id="id38">6.2 The Static Binary</a></li>
</ul>
</li>
-<li><a class="reference" href="#include-issues" id="id38"
name="id38">7 <tt class="docutils literal"><span
class="pre">#include</span></tt> Issues</a></li>
-<li><a class="reference" href="#python-debugging-builds" id="id39"
name="id39">8 Python Debugging Builds</a></li>
-<li><a class="reference" href="#testing-boost-python" id="id40"
name="id40">9 Testing Boost.Python</a></li>
-<li><a class="reference"
href="#notes-for-mingw-and-cygwin-with-mno-cygwin-gcc-users" id="id41"
name="id41">10 Notes for MinGW (and Cygwin with -mno-cygwin)
GCC Users</a></li>
+<li><a class="reference internal" href="#include-issues"
id="id39">7 <tt class="docutils literal"><span
class="pre">#include</span></tt> Issues</a></li>
+<li><a class="reference internal" href="#python-debugging-builds"
id="id40">8 Python Debugging Builds</a></li>
+<li><a class="reference internal" href="#testing-boost-python"
id="id41">9 Testing Boost.Python</a></li>
+<li><a class="reference internal"
href="#notes-for-mingw-and-cygwin-with-mno-cygwin-gcc-users"
id="id42">10 Notes for MinGW (and Cygwin with -mno-cygwin) GCC
Users</a></li>
</ul>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id24" id="requirements"
name="requirements">1 Requirements</a></h1>
-<p>Boost.Python requires <a class="reference"
href="http://www.python.org/2.2";>Python 2.2</a><a class="footnote-reference"
href="#id21" id="id2" name="id2"><sup>1</sup></a> <em>or</em> <a
class="reference" href="http://www.python.org";><em>newer</em></a>.</p>
+<div class="section" id="requirements">
+<h1><a class="toc-backref"
href="#id25">1 Requirements</a></h1>
+<p>Boost.Python requires <a class="reference external"
href="http://www.python.org/2.2";>Python 2.2</a><a class="footnote-reference"
href="#id22" id="id2"><sup>1</sup></a> <em>or</em> <a class="reference
external" href="http://www.python.org";><em>newer</em></a>.</p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id25" id="background"
name="background">2 Background</a></h1>
+<div class="section" id="background">
+<h1><a class="toc-backref" href="#id26">2 Background</a></h1>
<p>There are two basic models for combining C++ and Python:</p>
<ul class="simple">
-<li><a class="reference"
href="http://www.python.org/doc/current/ext/intro.html";>extending</a>, in which
the end-user launches the Python interpreter
+<li><a class="reference external"
href="http://www.python.org/doc/current/ext/intro.html";>extending</a>, in which
the end-user launches the Python interpreter
executable and imports Python âextension modulesâ written in C++.
Think of taking a library written in C++ and giving it a Python
interface so Python programmers can use it. From Python, these
modules look just like regular Python modules.</li>
-<li><a class="reference"
href="http://www.python.org/doc/current/ext/embedding.html";>embedding</a>, in
which the end-user launches a program written
+<li><a class="reference external"
href="http://www.python.org/doc/current/ext/embedding.html";>embedding</a>, in
which the end-user launches a program written
in C++ that in turn invokes the Python interpreter as a library
subroutine. Think of adding scriptability to an existing
application.</li>
@@ -65,7 +65,7 @@
<p>The key distinction between extending and embedding is the location
of the C++ <tt class="docutils literal"><span class="pre">main()</span></tt>
function: in the Python interpreter executable,
or in some other program, respectively. Note that even when
-embedding Python in another program, <a class="reference"
href="http://www.python.org/doc/current/ext/extending-with-embedding.html";>extension
modules are often
+embedding Python in another program, <a class="reference external"
href="http://www.python.org/doc/current/ext/extending-with-embedding.html";>extension
modules are often
the best way to make C/C++ functionality accessible to Python
code</a>, so the use of extension modules is really at the heart of
both models.</p>
@@ -74,10 +74,10 @@
you can change them without rebuilding either the other extension
modules or the executable containing <tt class="docutils literal"><span
class="pre">main()</span></tt>.</p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id26" id="no-install-quickstart"
name="no-install-quickstart">3 No-Install Quickstart</a></h1>
+<div class="section" id="no-install-quickstart">
+<h1><a class="toc-backref" href="#id27">3 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"
href="../../../tools/build/index.html">Boost.Build</a> projects,
+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
first tests may take a little longer while you wait for
Boost.Python to build, but doing things this way will save you from
@@ -105,20 +105,20 @@
<!-- .. raw:: html
</div> -->
-<div class="section">
-<h2><a class="toc-backref" href="#id27" id="basic-procedure"
name="basic-procedure">3.1 Basic Procedure</a></h2>
+<div class="section" id="basic-procedure">
+<h2><a class="toc-backref" href="#id28">3.1 Basic
Procedure</a></h2>
<ol class="arabic">
-<li><p class="first">Get Boost; see sections 1 and 2 [<a class="reference"
href="../../../more/getting_started/unix-variants.html#get-boost">Unix/Linux</a>,
<a class="reference"
href="../../../more/getting_started/windows.html#get-boost">Windows</a>] of the
-Boost <a class="reference"
href="../../../more/getting_started/index.html">Getting Started Guide</a>.</p>
+<li><p class="first">Get Boost; see sections 1 and 2 [<a class="reference
external"
href="../../../more/getting_started/unix-variants.html#get-boost">Unix/Linux</a>,
<a class="reference external"
href="../../../more/getting_started/windows.html#get-boost">Windows</a>] of the
+Boost <a class="reference external"
href="../../../more/getting_started/index.html">Getting Started Guide</a>.</p>
</li>
-<li><p class="first">Get the <tt class="docutils literal"><span
class="pre">bjam</span></tt> build driver. See section 5 [<a class="reference"
href="../../../more/getting_started/unix-variants.html#prepare-to-use-a-boost-library-binary">Unix/Linux</a>,
-<a class="reference"
href="../../../more/getting_started/windows.html#prepare-to-use-a-boost-library-binary">Windows</a>]
of the Boost <a class="reference"
href="../../../more/getting_started/index.html">Getting Started Guide</a>.</p>
+<li><p class="first">Get the <tt class="docutils literal"><span
class="pre">bjam</span></tt> build driver. See section 5 [<a class="reference
external"
href="../../../more/getting_started/unix-variants.html#prepare-to-use-a-boost-library-binary">Unix/Linux</a>,
+<a class="reference external"
href="../../../more/getting_started/windows.html#prepare-to-use-a-boost-library-binary">Windows</a>]
of the Boost <a class="reference external"
href="../../../more/getting_started/index.html">Getting Started Guide</a>.</p>
</li>
<li><p class="first">cd into the <tt class="docutils literal"><span
class="pre">libs/python/example/quickstart/</span></tt> directory of your
Boost installation, which contains a small example project.</p>
</li>
<li><p class="first">Invoke <tt class="docutils literal"><span
class="pre">bjam</span></tt>. Replace the â<tt class="docutils
literal"><span class="pre">stage</span></tt>â argument from the
-example invocation from section 5 of the <a class="reference"
href="../../../more/getting_started/index.html">Getting Started
+example invocation from section 5 of the <a class="reference external"
href="../../../more/getting_started/index.html">Getting Started
Guide</a> with â<tt class="docutils literal"><span
class="pre">test</span></tt>,â to build all the test targets. Also add
the argument â<tt class="docutils literal"><span
class="pre">--verbose-test</span></tt>â to see the output generated by
the tests when they are run.</p>
@@ -137,7 +137,7 @@
<p class="last">For the sake of concision, the rest of this guide will use
unix-style forward slashes in pathnames instead of the
backslashes with which you may be more familiar. The forward
-slashes should work everywhere except in <a class="reference"
href="../../../more/getting_started/windows.html#command-prompt">Command
Prompt</a>
+slashes should work everywhere except in <a class="reference external"
href="../../../more/getting_started/windows.html#command-prompt">Command
Prompt</a>
windows, where you should use backslashes.</p>
</div>
<p>If you followed this procedure successfully, you will have built an
@@ -146,55 +146,55 @@
built and run a simple application called <tt class="docutils literal"><span
class="pre">embedding</span></tt> that embeds
python.</p>
</div>
-<div class="section">
-<h2><a class="toc-backref" href="#id28" id="in-case-of-trouble"
name="in-case-of-trouble">3.2 In Case of Trouble</a></h2>
+<div class="section" id="in-case-of-trouble">
+<h2><a class="toc-backref" href="#id29">3.2 In Case of
Trouble</a></h2>
<p>If you're seeing lots of compiler and/or linker error messages,
it's probably because Boost.Build is having trouble finding your
Python installation. You might want to pass the
<tt class="docutils literal"><span
class="pre">--debug-configuration</span></tt> option to <tt class="docutils
literal"><span class="pre">bjam</span></tt> the first few times
you invoke it, to make sure that Boost.Build is correctly locating
all the parts of your Python installation. If it isn't, consider
-<a class="reference" href="#configuring-boost-build">Configuring
Boost.Build</a> as detailed below.</p>
+<a class="reference internal" href="#configuring-boost-build">Configuring
Boost.Build</a> as detailed below.</p>
<p>If you're still having trouble, Someone on one of the following
mailing lists may be able to help:</p>
<ul class="simple">
-<li>The <a class="reference"
href="../../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>
for issues related to Boost.Build</li>
-<li>The Python <a class="reference"
href="../../../more/mailing_lists.htm#cplussig">C++ Sig</a> for issues
specifically related to Boost.Python</li>
+<li>The <a class="reference external"
href="../../../more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>
for issues related to Boost.Build</li>
+<li>The Python <a class="reference external"
href="../../../more/mailing_lists.htm#cplussig">C++ Sig</a> for issues
specifically related to Boost.Python</li>
</ul>
</div>
-<div class="section">
-<h2><a class="toc-backref" href="#id29" id="in-case-everything-seemed-to-work"
name="in-case-everything-seemed-to-work">3.3 In Case
Everything Seemed to Work</a></h2>
+<div class="section" id="in-case-everything-seemed-to-work">
+<h2><a class="toc-backref" href="#id30">3.3 In Case
Everything Seemed to Work</a></h2>
<p>Rejoice! If you're new to Boost.Python, at this point it might be
a good idea to ignore build issues for a while and concentrate on
-learning the library by going through the <a class="reference"
href="tutorial/index.html">tutorial</a> and perhaps
-some of the <a class="reference" href="v2/reference.html">reference
documentation</a>, trying out what you've
+learning the library by going through the <a class="reference external"
href="tutorial/index.html">tutorial</a> and perhaps
+some of the <a class="reference external" href="v2/reference.html">reference
documentation</a>, trying out what you've
learned about the API by modifying the quickstart project.</p>
</div>
-<div class="section">
-<h2><a class="toc-backref" href="#id30" id="modifying-the-example-project"
name="modifying-the-example-project">3.4 Modifying the Example
Project</a></h2>
+<div class="section" id="modifying-the-example-project">
+<h2><a class="toc-backref" href="#id31">3.4 Modifying the
Example Project</a></h2>
<p>If you're content to keep your extension module forever in one
-source file called <a class="reference"
href="../example/quickstart/extending.cpp"><tt class="docutils literal"><span
class="pre">extending.cpp</span></tt></a>, inside your Boost
+source file called <a class="reference external"
href="../example/quickstart/extending.cpp"><tt class="docutils literal"><span
class="pre">extending.cpp</span></tt></a>, inside your Boost
distribution, and import it forever as <tt class="docutils literal"><span
class="pre">extending</span></tt>, then you can
stop here. However, it's likely that you will want to make a few
changes. There are a few things you can do without having to learn
-<a class="reference" href="../../../tools/build/index.html">Boost.Build</a> in
depth.</p>
+<a class="reference external"
href="../../../tools/build/index.html">Boost.Build</a> in depth.</p>
<p>The project you just built is specified in two files in the current
-directory: <a class="reference"
href="../example/quickstart/boost-build.jam"><tt class="docutils literal"><span
class="pre">boost-build.jam</span></tt></a>, which tells <tt class="docutils
literal"><span class="pre">bjam</span></tt> where it can
+directory: <a class="reference external"
href="../example/quickstart/boost-build.jam"><tt class="docutils literal"><span
class="pre">boost-build.jam</span></tt></a>, which tells <tt class="docutils
literal"><span class="pre">bjam</span></tt> where it can
find the interpreted code of the Boost build system, and
-<a class="reference" href="../example/quickstart/Jamroot"><tt class="docutils
literal"><span class="pre">Jamroot</span></tt></a>, which describes the targets
you just built. These
+<a class="reference external" href="../example/quickstart/Jamroot"><tt
class="docutils literal"><span class="pre">Jamroot</span></tt></a>, which
describes the targets you just built. These
files are heavily commented, so they should be easy to modify.
Take care, however, to preserve whitespace. Punctuation such as
<tt class="docutils literal"><span class="pre">;</span></tt> will not be
recognized as intended by <tt class="docutils literal"><span
class="pre">bjam</span></tt> if it is not
surrounded by whitespace.</p>
-<div class="section">
-<h3><a id="relocate-the-project" name="relocate-the-project">Relocate the
Project</a></h3>
+<div class="section" id="relocate-the-project">
+<h3>Relocate the Project</h3>
<p>You'll probably want to copy this project elsewhere so you can
change it without modifying your Boost distribution. To do that,
simply</p>
<ol class="loweralpha simple">
<li>copy the entire <tt class="docutils literal"><span
class="pre">libs/python/example/quickstart/</span></tt> directory
into a new directory.</li>
-<li>In the new copies of <a class="reference"
href="../example/quickstart/boost-build.jam"><tt class="docutils literal"><span
class="pre">boost-build.jam</span></tt></a> and <a class="reference"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a>, locate
+<li>In the new copies of <a class="reference external"
href="../example/quickstart/boost-build.jam"><tt class="docutils literal"><span
class="pre">boost-build.jam</span></tt></a> and <a class="reference external"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a>, locate
the relative path near the top of the file that is clearly
marked by a comment, and edit that path so that it refers to the
same directory your Boost distribution as it referred to when
@@ -204,7 +204,7 @@
<p>For example, if you moved the project from
<tt class="docutils literal"><span
class="pre">/home/dave/boost_1_34_0/libs/python/example/quickstart</span></tt>
to
<tt class="docutils literal"><span
class="pre">/home/dave/my-project</span></tt>, you could change the first path
in
-<a class="reference" href="../example/quickstart/boost-build.jam"><tt
class="docutils literal"><span class="pre">boost-build.jam</span></tt></a>
from</p>
+<a class="reference external" href="../example/quickstart/boost-build.jam"><tt
class="docutils literal"><span class="pre">boost-build.jam</span></tt></a>
from</p>
<pre class="literal-block">
<strong>../../../..</strong>/tools/build/v2
</pre>
@@ -212,7 +212,7 @@
<pre class="literal-block">
<strong>/home/dave/boost_1_34_0</strong>/tools/build/v2
</pre>
-<p>and change the first path in <a class="reference"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a> from</p>
+<p>and change the first path in <a class="reference external"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a> from</p>
<pre class="literal-block">
<strong>../../../..</strong>
</pre>
@@ -221,28 +221,28 @@
<strong>/home/dave/boost_1_34_0</strong>
</pre>
</div>
-<div class="section">
-<h3><a id="add-new-or-change-names-of-existing-source-files"
name="add-new-or-change-names-of-existing-source-files">Add New or Change Names
of Existing Source Files</a></h3>
+<div class="section" id="add-new-or-change-names-of-existing-source-files">
+<h3>Add New or Change Names of Existing Source Files</h3>
<p>The names of additional source files involved in building your
extension module or embedding application can be listed in
-<a class="reference" href="../example/quickstart/Jamroot"><tt class="docutils
literal"><span class="pre">Jamroot</span></tt></a> right alongside <tt
class="docutils literal"><span class="pre">extending.cpp</span></tt> or <tt
class="docutils literal"><span class="pre">embedding.cpp</span></tt>
+<a class="reference external" href="../example/quickstart/Jamroot"><tt
class="docutils literal"><span class="pre">Jamroot</span></tt></a> right
alongside <tt class="docutils literal"><span
class="pre">extending.cpp</span></tt> or <tt class="docutils literal"><span
class="pre">embedding.cpp</span></tt>
respectively. Just be sure to leave whitespace around each
filename:</p>
<pre class="literal-block">
⦠file1.cpp file2.cpp file3.cpp â¦
</pre>
<p>Naturally, if you want to change the name of a source file you can
-tell Boost.Build about it by editing the name in <a class="reference"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a>.</p>
+tell Boost.Build about it by editing the name in <a class="reference external"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a>.</p>
</div>
-<div class="section">
-<h3><a id="change-the-name-of-your-extension-module"
name="change-the-name-of-your-extension-module">Change the Name of your
Extension Module</a></h3>
+<div class="section" id="change-the-name-of-your-extension-module">
+<h3>Change the Name of your Extension Module</h3>
<p>The name of the extension module is determined by two things:</p>
<ol class="arabic simple">
-<li>the name in <a class="reference" href="../example/quickstart/Jamroot"><tt
class="docutils literal"><span class="pre">Jamroot</span></tt></a> immediately
following <tt class="docutils literal"><span
class="pre">python-extension</span></tt>, and</li>
-<li>the name passed to <tt class="docutils literal"><span
class="pre">BOOST_PYTHON_MODULE</span></tt> in <a class="reference"
href="../example/quickstart/extending.cpp"><tt class="docutils literal"><span
class="pre">extending.cpp</span></tt></a>.</li>
+<li>the name in <a class="reference external"
href="../example/quickstart/Jamroot"><tt class="docutils literal"><span
class="pre">Jamroot</span></tt></a> immediately following <tt class="docutils
literal"><span class="pre">python-extension</span></tt>, and</li>
+<li>the name passed to <tt class="docutils literal"><span
class="pre">BOOST_PYTHON_MODULE</span></tt> in <a class="reference external"
href="../example/quickstart/extending.cpp"><tt class="docutils literal"><span
class="pre">extending.cpp</span></tt></a>.</li>
</ol>
<p>To change the name of the extension module from <tt class="docutils
literal"><span class="pre">extending</span></tt> to
-<tt class="docutils literal"><span class="pre">hello</span></tt>, you'd edit
<a class="reference" href="../example/quickstart/Jamroot"><tt class="docutils
literal"><span class="pre">Jamroot</span></tt></a>, changing</p>
+<tt class="docutils literal"><span class="pre">hello</span></tt>, you'd edit
<a class="reference external" href="../example/quickstart/Jamroot"><tt
class="docutils literal"><span class="pre">Jamroot</span></tt></a>, changing</p>
<pre class="literal-block">
python-extension <strong>extending</strong> : extending.cpp ;
</pre>
@@ -261,13 +261,13 @@
</div>
</div>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id31"
id="installing-boost-python-on-your-system"
name="installing-boost-python-on-your-system">4 Installing
Boost.Python on your System</a></h1>
+<div class="section" id="installing-boost-python-on-your-system">
+<h1><a class="toc-backref" href="#id32">4 Installing
Boost.Python on your System</a></h1>
<p>Since Boost.Python is a separately-compiled (as opposed to
-<a class="reference"
href="../../../more/getting_started/windows.html#header-only-libraries">header-only</a>)
library, its user relies on the services of a
+<a class="reference external"
href="../../../more/getting_started/windows.html#header-only-libraries">header-only</a>)
library, its user relies on the services of a
Boost.Python library binary.</p>
<p>If you need a regular installation of the Boost.Python library
-binaries on your system, the Boost <a class="reference"
href="../../../more/getting_started/index.html">Getting Started Guide</a> will
+binaries on your system, the Boost <a class="reference external"
href="../../../more/getting_started/index.html">Getting Started Guide</a> will
walk you through the steps of creating one. If building binaries
from source, you might want to supply the <tt class="docutils literal"><span
class="pre">--with-python</span></tt>
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
@@ -275,17 +275,17 @@
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"
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"
href="#no-install-quickstart">quickstart</a> method, you'll have to pay
+<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"
href="../../../more/getting_started/index.html">Getting Started Guide</a> to
select the
+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">
-<h1><a class="toc-backref" href="#id32" id="configuring-boost-build"
name="configuring-boost-build">5 Configuring
Boost.Build</a></h1>
-<p>As described in the <a class="reference"
href="http://www.boost.orgdoc/html/bbv2/advanced.html#bbv2.advanced.configuration";>Boost.Build
reference manual</a>, a file called
-<tt class="docutils literal"><span class="pre">user-config.jam</span></tt> in
your home directory<a class="footnote-reference" href="#home-dir" id="id11"
name="id11"><sup>6</sup></a> is used to
+<div class="section" id="configuring-boost-build">
+<h1><a class="toc-backref" href="#id33">5 Configuring
Boost.Build</a></h1>
+<p>As described in the <a class="reference external"
href="http://www.boost.orgdoc/html/bbv2/advanced.html#bbv2.advanced.configuration";>Boost.Build
reference manual</a>, a file called
+<tt class="docutils literal"><span class="pre">user-config.jam</span></tt> in
your home directory<a class="footnote-reference" href="#home-dir"
id="id11"><sup>6</sup></a> is used to
specify the tools and libraries available to the build system. You
may need to create or edit <tt class="docutils literal"><span
class="pre">user-config.jam</span></tt> to tell Boost.Build
how to invoke Python, <tt class="docutils literal"><span
class="pre">#include</span></tt> its headers, and link with its
@@ -294,7 +294,7 @@
<p class="first admonition-title">Users of Unix-Variant OSes</p>
<p class="last">If you are using a unix-variant OS and you ran Boost's
<tt class="docutils literal"><span class="pre">configure</span></tt> script,
it may have generated a
-<tt class="docutils literal"><span class="pre">user-config.jam</span></tt> for
you.<a class="footnote-reference" href="#overwrite" id="id13"
name="id13"><sup>4</sup></a> If your <tt class="docutils literal"><span
class="pre">configure</span></tt>/<tt class="docutils literal"><span
class="pre">make</span></tt> sequence was successful and Boost.Python binaries
+<tt class="docutils literal"><span class="pre">user-config.jam</span></tt> for
you.<a class="footnote-reference" href="#overwrite" id="id13"><sup>4</sup></a>
If your <tt class="docutils literal"><span
class="pre">configure</span></tt>/<tt class="docutils literal"><span
class="pre">make</span></tt> sequence was successful and Boost.Python binaries
were built, your <tt class="docutils literal"><span
class="pre">user-config.jam</span></tt> file is probably already
correct.</p>
</div>
@@ -309,12 +309,12 @@
</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"
href="#no-install-quickstart">quickstart</a>
+(e.g. when referred to by another project as in the <a class="reference
internal" href="#no-install-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>
-<div class="section">
-<h2><a class="toc-backref" href="#id33" id="python-configuration-parameters"
name="python-configuration-parameters">5.1 Python
Configuration Parameters</a></h2>
+<div class="section" id="python-configuration-parameters">
+<h2><a class="toc-backref" href="#id34">5.1 Python
Configuration Parameters</a></h2>
<p>If you have several versions of Python installed, or Python is
installed in an unusual way, you may want to supply any or all of
the following optional parameters to <tt class="docutils literal"><span
class="pre">using</span> <span class="pre">python</span></tt>.</p>
@@ -350,13 +350,13 @@
don't need to use this. Usually this suffix is only used when
targeting a Windows debug build of Python, and will be set
automatically for you based on the value of the
-<a class="reference" href="#python-debugging"><tt class="docutils
literal"><span class="pre"><python-debugging></span></tt></a> feature.
However, at least one Linux
+<a class="reference internal" href="#python-debugging"><tt class="docutils
literal"><span class="pre"><python-debugging></span></tt></a> feature.
However, at least one Linux
distribution (Ubuntu Feisty Fawn) has a specially configured
-<a class="reference" href="https://wiki.ubuntu.com/PyDbgBuilds";>python-dbg</a>
package that claims to use such a suffix.</dd>
+<a class="reference external"
href="https://wiki.ubuntu.com/PyDbgBuilds";>python-dbg</a> package that claims
to use such a suffix.</dd>
</dl>
</div>
-<div class="section">
-<h2><a class="toc-backref" href="#id34" id="examples"
name="examples">5.2 Examples</a></h2>
+<div class="section" id="examples">
+<h2><a class="toc-backref" href="#id35">5.2 Examples</a></h2>
<p>Note that in the examples below, case and <em>especially whitespace</em> are
significant.</p>
<ul>
@@ -395,7 +395,7 @@
</pre>
</li>
<li><p class="first">If you have downloaded the Python sources and built both
the
-normal and the â<a class="reference" href="#id19">python debugging</a>â
builds from source on
+normal and the â<a class="reference internal" href="#id19">python
debugging</a>â builds from source on
Windows, you might see:</p>
<pre class="literal-block">
using python : 2.5 : C:\\src\\Python-2.5\\PCBuild\\python ;
@@ -406,7 +406,7 @@
</pre>
</li>
<li><p class="first">You can set up your user-config.jam so a bjam built under
Windows
-can build/test both Windows and <a class="reference"
href="http://cygwin.com";>Cygwin</a> python extensions. Just pass
+can build/test both Windows and <a class="reference external"
href="http://cygwin.com";>Cygwin</a> python extensions. Just pass
<tt class="docutils literal"><span
class="pre"><target-os>cygwin</span></tt> in the <tt class="docutils
literal"><span class="pre">condition</span></tt> parameter
for the cygwin python installation:</p>
<pre class="literal-block">
@@ -417,16 +417,16 @@
using python : : c:\\cygwin\\bin\\python2.5 : : : <target-os>cygwin ;
</pre>
<p>when you put target-os=cygwin in your build request, it should build
-with the cygwin version of python:<a class="footnote-reference" href="#flavor"
id="id15" name="id15"><sup>5</sup></a></p>
+with the cygwin version of python:<a class="footnote-reference" href="#flavor"
id="id15"><sup>5</sup></a></p>
<blockquote>
<p>bjam target-os=cygwin toolset=gcc</p>
</blockquote>
<p>This is supposed to work the other way, too (targeting windows
-python with a <a class="reference" href="http://cygwin.com";>Cygwin</a> bjam)
but it seems as though the support in
+python with a <a class="reference external"
href="http://cygwin.com";>Cygwin</a> bjam) but it seems as though the support in
Boost.Build's toolsets for building that way is broken at the
time of this writing.</p>
</li>
-<li><p class="first">Note that because of <a class="reference"
href="http://zigzag.cs.msu.su/boost.build/wiki/AlternativeSelection";>the way
Boost.Build currently selects target
+<li><p class="first">Note that because of <a class="reference external"
href="http://zigzag.cs.msu.su/boost.build/wiki/AlternativeSelection";>the way
Boost.Build currently selects target
alternatives</a>, you might have be very explicit in your build
requests. For example, given:</p>
<pre class="literal-block">
@@ -445,35 +445,35 @@
</ul>
</div>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id35"
id="choosing-a-boost-python-library-binary"
name="choosing-a-boost-python-library-binary">6 Choosing a
Boost.Python Library Binary</a></h1>
+<div class="section" id="choosing-a-boost-python-library-binary">
+<h1><a class="toc-backref" href="#id36">6 Choosing a
Boost.Python Library Binary</a></h1>
<p>Ifâinstead of letting Boost.Build construct and link with the right
libraries automaticallyâyou choose to use a pre-built Boost.Python
library, you'll need to think about which one to link with. The
Boost.Python binary comes in both static and dynamic flavors. Take
-care to choose the right flavor for your application.<a
class="footnote-reference" href="#naming" id="id17"
name="id17"><sup>2</sup></a></p>
-<div class="section">
-<h2><a class="toc-backref" href="#id36" id="the-dynamic-binary"
name="the-dynamic-binary">6.1 The Dynamic Binary</a></h2>
+care to choose the right flavor for your application.<a
class="footnote-reference" href="#naming" id="id17"><sup>2</sup></a></p>
+<div class="section" id="the-dynamic-binary">
+<h2><a class="toc-backref" href="#id37">6.1 The Dynamic
Binary</a></h2>
<p>The dynamic library is the safest and most-versatile choice:</p>
<ul class="simple">
<li>A single copy of the library code is used by all extension
-modules built with a given toolset.<a class="footnote-reference"
href="#toolset-specific" id="id18" name="id18"><sup>3</sup></a></li>
+modules built with a given toolset.<a class="footnote-reference"
href="#toolset-specific" id="id18"><sup>3</sup></a></li>
<li>The library contains a type conversion registry. Because one
registry is shared among all extension modules, instances of a
class exposed to Python in one dynamically-loaded extension
module can be passed to functions exposed in another such module.</li>
</ul>
</div>
-<div class="section">
-<h2><a class="toc-backref" href="#id37" id="the-static-binary"
name="the-static-binary">6.2 The Static Binary</a></h2>
+<div class="section" id="the-static-binary">
+<h2><a class="toc-backref" href="#id38">6.2 The Static
Binary</a></h2>
<p>It might be appropriate to use the static Boost.Python library in
any of the following cases:</p>
<ul class="simple">
-<li>You are <a class="reference"
href="http://www.python.org/doc/current/ext/intro.html";>extending</a> python
and the types exposed in your
+<li>You are <a class="reference external"
href="http://www.python.org/doc/current/ext/intro.html";>extending</a> python
and the types exposed in your
dynamically-loaded extension module don't need to be used by any
other Boost.Python extension modules, and you don't care if the
core library code is duplicated among them.</li>
-<li>You are <a class="reference"
href="http://www.python.org/doc/current/ext/embedding.html";>embedding</a>
python in your application and either:<ul>
+<li>You are <a class="reference external"
href="http://www.python.org/doc/current/ext/embedding.html";>embedding</a>
python in your application and either:<ul>
<li>You are targeting a Unix variant OS other than MacOS or AIX,
where the dynamically-loaded extension modules can âseeâ the
Boost.Python library symbols that are part of the executable.</li>
@@ -487,8 +487,8 @@
</ul>
</div>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id38" id="include-issues"
name="include-issues">7 <tt class="docutils literal"><span
class="pre">#include</span></tt> Issues</a></h1>
+<div class="section" id="include-issues">
+<h1><a class="toc-backref" href="#id39">7 <tt class="docutils
literal"><span class="pre">#include</span></tt> Issues</a></h1>
<ol class="arabic simple">
<li>If you should ever have occasion to <tt class="docutils literal"><span
class="pre">#include</span> <span class="pre">"python.h"</span></tt>
directly in a translation unit of a program using Boost.Python,
@@ -499,11 +499,11 @@
<tt class="docutils literal"><span class="pre">wrap_python.hpp</span></tt>.
This restriction is actually imposed by
Python, or more properly, by Python's interaction with your
operating system. See
-<a class="reference"
href="http://docs.python.org/ext/simpleExample.html";>http://docs.python.org/ext/simpleExample.html</a>
for details.</li>
+<a class="reference external"
href="http://docs.python.org/ext/simpleExample.html";>http://docs.python.org/ext/simpleExample.html</a>
for details.</li>
</ol>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id39" id="python-debugging-builds"
name="python-debugging-builds"><span id="id19"></span><span
id="python-debugging"></span>8 Python Debugging Builds</a></h1>
+<div class="section" id="python-debugging-builds">
+<span id="id19"></span><span id="python-debugging"></span><h1><a
class="toc-backref" href="#id40">8 Python Debugging
Builds</a></h1>
<p>Python can be built in a special âpython debuggingâ configuration
that adds extra checks and instrumentation that can be very useful
for developers of extension modules. The data structures used by
@@ -513,7 +513,7 @@
vice-versa.</strong></p>
<p>Since pre-built âpython debuggingâ versions of the Python
executable and libraries are not supplied with most distributions
-of Python, [#get-debug-build] and we didn't want to force our users
+of Python,<a class="footnote-reference" href="#get-debug-build"
id="id20"><sup>7</sup></a> and we didn't want to force our users
to build them, Boost.Build does not automatically enable python
debugging in its <tt class="docutils literal"><span
class="pre">debug</span></tt> build variant (which is the default).
Instead there is a special build property called
@@ -533,27 +533,27 @@
sure <tt class="docutils literal"><span
class="pre">BOOST_DEBUG_PYTHON</span></tt> is defined, or python debugging will
be
suppressed.</p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id40" id="testing-boost-python"
name="testing-boost-python">9 Testing Boost.Python</a></h1>
+<div class="section" id="testing-boost-python">
+<h1><a class="toc-backref" href="#id41">9 Testing
Boost.Python</a></h1>
<p>To run the full test suite for Boost.Python, invoke <tt class="docutils
literal"><span class="pre">bjam</span></tt> in the
<tt class="docutils literal"><span class="pre">libs/python/test</span></tt>
subdirectory of your Boost distribution.</p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id41"
id="notes-for-mingw-and-cygwin-with-mno-cygwin-gcc-users"
name="notes-for-mingw-and-cygwin-with-mno-cygwin-gcc-users">10 Notes
for MinGW (and Cygwin with -mno-cygwin) GCC Users</a></h1>
+<div class="section" id="notes-for-mingw-and-cygwin-with-mno-cygwin-gcc-users">
+<h1><a class="toc-backref" href="#id42">10 Notes for MinGW
(and Cygwin with -mno-cygwin) GCC Users</a></h1>
<p>If you are using a version of Python prior to 2.4.1 with a MinGW
prior to 3.0.0 (with binutils-2.13.90-20030111-1), you will need to
create a MinGW-compatible version of the Python library; the one
shipped with Python will only work with a Microsoft-compatible
linker. Follow the instructions in the âNon-Microsoftâ section of
-the âBuilding Extensions: Tips And Tricksâ chapter in <a class="reference"
href="http://www.python.org/doc/current/inst/index.html";>Installing
+the âBuilding Extensions: Tips And Tricksâ chapter in <a class="reference
external" href="http://www.python.org/doc/current/inst/index.html";>Installing
Python Modules</a> to create <tt class="docutils literal"><span
class="pre">libpythonXX.a</span></tt>, where <tt class="docutils literal"><span
class="pre">XX</span></tt>
corresponds to the major and minor version numbers of your Python
installation.</p>
<hr class="docutils" />
-<table class="docutils footnote" frame="void" id="id21" rules="none">
+<table class="docutils footnote" frame="void" id="id22" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a class="fn-backref" href="#id2"
name="id21">[1]</a></td><td>Note that although we tested earlier versions of
+<tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>Note
that although we tested earlier versions of
Boost.Python with Python 2.2, and we don't <em>think</em> we've done
anything to break compatibility, this release of Boost.Python
may not have been tested with versions of Python earlier than
@@ -564,11 +564,11 @@
<table class="docutils footnote" frame="void" id="naming" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a class="fn-backref" href="#id17"
name="naming">[2]</a></td><td><p class="first">Information about how to
identify the
+<tr><td class="label"><a class="fn-backref" href="#id17">[2]</a></td><td><p
class="first">Information about how to identify the
static and dynamic builds of Boost.Python:</p>
<ul class="simple">
-<li><a class="reference"
href="../../../more/getting_started/windows.html#library-naming">on
Windows</a></li>
-<li><a class="reference"
href="../../../more/getting_started/unix-variants.html#library-naming">on Unix
variants</a></li>
+<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
@@ -579,7 +579,7 @@
<table class="docutils footnote" frame="void" id="toolset-specific"
rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a class="fn-backref" href="#id18"
name="toolset-specific">[3]</a></td><td>Because of the way most *nix platforms
+<tr><td class="label"><a class="fn-backref"
href="#id18">[3]</a></td><td>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
will always use different copies of the Boost.Python library
@@ -596,7 +596,7 @@
<table class="docutils footnote" frame="void" id="overwrite" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a class="fn-backref" href="#id13"
name="overwrite">[4]</a></td><td><tt class="docutils literal"><span
class="pre">configure</span></tt> overwrites the existing
+<tr><td class="label"><a class="fn-backref" href="#id13">[4]</a></td><td><tt
class="docutils literal"><span class="pre">configure</span></tt> overwrites the
existing
<tt class="docutils literal"><span class="pre">user-config.jam</span></tt> in
your home directory
(if any) after making a backup of the old version.</td></tr>
</tbody>
@@ -604,7 +604,7 @@
<table class="docutils footnote" frame="void" id="flavor" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a class="fn-backref" href="#id15"
name="flavor">[5]</a></td><td>Note that the <tt class="docutils literal"><span
class="pre"><target-os>cygwin</span></tt> feature is
+<tr><td class="label"><a class="fn-backref" href="#id15">[5]</a></td><td>Note
that the <tt class="docutils literal"><span
class="pre"><target-os>cygwin</span></tt> feature is
different from the <tt class="docutils literal"><span
class="pre"><flavor>cygwin</span></tt> subfeature of the <tt
class="docutils literal"><span class="pre">gcc</span></tt>
toolset, and you might need handle both explicitly if you also
have a MinGW GCC installed.</td></tr>
@@ -613,19 +613,19 @@
<table class="docutils footnote" frame="void" id="home-dir" rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a class="fn-backref" href="#id11"
name="home-dir">[6]</a></td><td><p class="first">Windows users, your home
directory can be
+<tr><td class="label"><a class="fn-backref" href="#id11">[6]</a></td><td><p
class="first">Windows users, your home directory can be
found by typing:</p>
<pre class="literal-block">
ECHO %HOMEDRIVE%%HOMEPATH%
</pre>
-<p class="last">into a <a class="reference"
href="../../../more/getting_started/windows.html#command-prompt">command
prompt</a> window.</p>
+<p class="last">into a <a class="reference external"
href="../../../more/getting_started/windows.html#command-prompt">command
prompt</a> window.</p>
</td></tr>
</tbody>
</table>
<table class="docutils footnote" frame="void" id="get-debug-build"
rules="none">
<colgroup><col class="label" /><col /></colgroup>
<tbody valign="top">
-<tr><td class="label"><a name="get-debug-build">[7]</a></td><td>On Unix and
similar platforms, a debugging
+<tr><td class="label"><a class="fn-backref" href="#id20">[7]</a></td><td>On
Unix and similar platforms, a debugging
python and associated libraries are built by adding
<tt class="docutils literal"><span class="pre">--with-pydebug</span></tt> when
configuring the Python build. On
Windows, the debugging version of Python is generated by
@@ -638,9 +638,9 @@
</div>
<div class="footer">
<hr class="footer" />
-<a class="reference" href="./building.rst">View document source</a>.
-Generated on: 2007-05-04 00:01 UTC.
-Generated by <a class="reference"
href="http://docutils.sourceforge.net/";>Docutils</a> from <a class="reference"
href="http://docutils.sourceforge.net/rst.html";>reStructuredText</a> source.
+<a class="reference external" href="./building.rst">View document source</a>.
+Generated on: 2007-05-07 18:58 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>
</body>
Index: Jamfile
===================================================================
RCS file: /cvsroot/boost/boost/libs/python/doc/Jamfile,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -d -r1.1.2.2 -r1.1.2.3
--- Jamfile 4 May 2007 00:56:22 -0000 1.1.2.2
+++ Jamfile 7 May 2007 19:00:01 -0000 1.1.2.3
@@ -19,7 +19,5 @@
;
}
-exe tst : tst.cpp ;
-
alias htmls : $(bases) ;
stage . : $(bases) ;
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Boost-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/boost-cvs
