lambda-z
diff --git a/‎doc/Jamfile‎
Lines changed: 2 additions & 0 deletions b/‎doc/Jamfile‎
Lines changed: 2 additions & 0 deletions
diff --git a/‎doc/building.html‎
Lines changed: 202 additions & 123 deletions b/‎doc/building.html‎
Lines changed: 202 additions & 123 deletions
diff --git a/‎doc/building.rst‎
Lines changed: 85 additions & 7 deletions b/‎doc/building.rst‎
Lines changed: 85 additions & 7 deletions
diff --git a/‎example/Attic/project.zip‎
-1.43 KB b/‎example/Attic/project.zip‎
-1.43 KB
diff --git a/‎example/Jamfile.v2‎
Lines changed: 0 additions & 36 deletions b/‎example/Jamfile.v2‎
Lines changed: 0 additions & 36 deletions
diff --git a/‎example/Jamrules‎
Lines changed: 0 additions & 36 deletions b/‎example/Jamrules‎
Lines changed: 0 additions & 36 deletions
diff --git a/‎example/quickstart/Jamroot‎
Lines changed: 33 additions & 0 deletions b/‎example/quickstart/Jamroot‎
Lines changed: 33 additions & 0 deletions
diff --git a/‎example/quickstart/boost-build.jam‎
Lines changed: 7 additions & 0 deletions b/‎example/quickstart/boost-build.jam‎
Lines changed: 7 additions & 0 deletions
@@ -19,5 +19,7 @@ for local b in $(bases)
   ;
 }
 
+exe tst : tst.cpp ;
+
 alias htmls : $(bases) ;
 stage . : $(bases) ;
@@ -169,6 +169,15 @@ you invoke it, to make sure that Boost.Build is correctly locating
 all the parts of your Python installation.  If it isn't, consider
 `Configuring Boost.Build`_ as detailed below.
 
+If you're still having trouble, Someone on one of the following
+mailing lists may be able to help:
+
+* The `Boost.Build mailing list`__ for issues related to Boost.Build
+* The Python `C++ Sig`__ for issues specifically related to Boost.Python
+
+__ ../../../more/mailing_lists.htm#jamboost
+__ ../../../more/mailing_lists.htm#cplussig
+
 In Case Everything Seemed to Work
 ---------------------------------
 
@@ -409,10 +418,12 @@ extension-suffix
   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
-  ``<python-debugging>`` feature.  However, at least one Linux
+  |python-debugging|_ feature.  However, at least one Linux
   distribution (Ubuntu Feisty Fawn) has a specially configured
   `python-dbg`__ package that claims to use such a suffix.
 
+.. |python-debugging| replace:: ``<python-debugging>``
+
 __ https://wiki.ubuntu.com/PyDbgBuilds
 
 
@@ -454,6 +465,17 @@ significant.
          : <toolset>intel # condition
          ;
 
+
+- If you have downloaded the Python sources and built both the
+  normal and the “\ `python debugging`_\ ” builds from source on
+  Windows, you might see::
+
+    using python : 2.5 : C:\\src\\Python-2.5\\PCBuild\\python ;
+    using python : 2.5 : C:\\src\\Python-2.5\\PCBuild\\python_d
+      : # includes
+      : # libs
+      : <python-debugging>on ;
+
 - You can set up your user-config.jam so a bjam built under Windows 
   can build/test both Windows and Cygwin_ python extensions.  Just pass
   ``<target-os>cygwin`` in the ``condition`` parameter
@@ -539,14 +561,63 @@ any of the following cases:
     use the types exposed by your statically-linked extension
     modules (and vice-versa).
 
-Testing Boost.Python
-====================
+``#include`` Issues
+===================
 
+1. If you should ever have occasion to ``#include "python.h"``
+   directly in a translation unit of a program using Boost.Python,
+   use ``#include "boost/python/detail/wrap_python.hpp"`` instead.
+   It handles several issues necessary for use with Boost.Python,
+   one of which is mentioned in the next section.
 
-Python Debug Builds
-===================
+2. Be sure not to ``#include`` any system headers before
+   ``wrap_python.hpp``.  This restriction is actually imposed by
+   Python, or more properly, by Python's interaction with your
+   operating system.  See
+   http://docs.python.org/ext/simpleExample.html for details.
+
+.. _python-debugging:
+.. _python debugging:
+
+Python Debugging Builds
+=======================
+
+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
+the debugging configuration contain additional members, so **a
+Python executable built with python debugging enabled cannot be
+used with an extension module or library compiled without it, and
+vice-versa.**
+
+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
+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
+``python-debugging`` that, when used as a build property, will
+define the right preprocessor symbols and select the right
+libraries to link with.
+
+On unix-variant platforms, the debugging versions of Python's data
+structures will only be used if the symbol ``Py_DEBUG`` is defined.
+On many windows compilers, when extension modules are built with
+the preprocessor symbol ``_DEBUG``, Python defaults to force
+linking with a special debugging version of the Python DLL.  Since
+that symbol is very commonly used even when Python is not present,
+Boost.Python temporarily undefines _DEBUG when Python.h
+is #included from ``boost/python/detail/wrap_python.hpp`` - unless
+``BOOST_DEBUG_PYTHON`` is defined.  The upshot is that if you want
+“python debugging”and you aren't using Boost.Build, you should make
+sure ``BOOST_DEBUG_PYTHON`` is defined, or python debugging will be
+suppressed.
 
+Testing Boost.Python
+====================
 
+To run the full test suite for Boost.Python, invoke ``bjam`` in the
+``libs/python/test`` subdirectory of your Boost distribution.
 
 Notes for MinGW (and Cygwin with -mno-cygwin) GCC Users
 =======================================================
@@ -586,8 +657,8 @@ __ http://www.python.org/doc/current/inst/index.html
    that feature.
 
 .. [#toolset-specific] Because of the way most \*nix platforms
-   share symbols among dynamically-loaded objects, I'm not
-   certainextension modules built with different compiler toolsets
+   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
    when loaded into the same Python instance.  Not using different
    libraries could be a good thing if the compilers have compatible
@@ -614,3 +685,10 @@ __ http://www.python.org/doc/current/inst/index.html
 
    into a `command prompt`_ window.
 
+.. [#get-debug-build] On Unix and similar platforms, a debugging
+   python and associated libraries are built by adding
+   ``--with-pydebug`` when configuring the Python build. On
+   Windows, the debugging version of Python is generated by
+   the "Win32 Debug" target of the Visual Studio project in the
+   PCBuild subdirectory of a full Python source code distribution.
+   You may also find
@@ -0,0 +1,33 @@
+# 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)
+
+# Specify the path to the Boost project.  If you move this project,
+# adjust the path to refer to the Boost root directory.
+use-project boost 
+  : ../../../.. ;
+
+# Set up the project-wide requirements that everything uses the
+# boost_python library defined in the project whose global ID is
+# /boost/python.
+project
+  : requirements <library>/boost/python//boost_python ;
+
+# Declare a Python extension called hello.
+python-extension extending : extending.cpp ;
+
+# Declare an executable called embedding that embeds Python
+exe embedding : embedding.cpp /python//python ;
+
+import testing ;
+
+# Declare a test of the extension module
+testing.make-test run-pyd : extending test_extending.py : : test_ext ;
+
+# Declare a test of the embedding application
+testing.run embedding 
+  :              # any ordinary arguments
+  : script.py    # any arguments that should be treated as relative paths
+  :              # requirements
+  : test_embed ; # name of test
+
@@ -0,0 +1,7 @@
+# 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)
+
+# Edit this path to point at the tools/build/v2 subdirectory of your
+# Boost installation.  Absolute paths work, too.
+boost-build ../../../../tools/build/v2 ;
Original file line number	Diff line number	Diff line change
`@@ -19,5 +19,7 @@ for local b in $(bases)`
`19`	`19`	`;`
`20`	`20`	`}`
`21`	`21`
	`22`	`+exe tst : tst.cpp ;`
	`23`	`+`
`22`	`24`	`alias htmls : $(bases) ;`
`23`	`25`	`stage . : $(bases) ;`