Building and Testing
Normally, Boost.Python extension modules must be linked with the
boost_python shared library. In special circumstances you
may want to link to a static version of the
library, but if multiple Boost.Python extension modules are used
together, it will prevent sharing of types across extension modules, and
consume extra code space. To build
boost_python, use Boost.Build in the usual way
libs/python/build subdirectory of your boost
installation (if you have already built boost from the top level this may
have no effect, since the work is already done).
||The root directory of your Python installation||Windows:
||On Unix, this is the
||The The 2-part python Major.Minor version number||
||Be sure not to include a third number, e.g. not
||path to Python
||path to Python library object.||Autoconfigured from
bjam. If "
bjam -v" does not report "
OS=NT", these settings do not apply to you; you should use the normal configuration variables instead. They are only useful when building and testing with multiple toolsets on Windows using a single build command, since Cygwin GCC requires a different build of Python.
||The version of python being used under Cygwin.||$(PYTHON_VERSION)|
||unix-style path containing the
||path containing the user's Cygwin Python import lib
||path containing the user's Cygwin Python dll
If you are using Cygwin GCC to build extension modules, you must use a Cygwin build of Python. The regular Win32 Python installation that you can download from python.org will not work with your compiler because the dynamic linking conventions are different (you can use MinGW GCC if you want to build extension modules which are compatible with a stock Win32 Python). The Cygwin installer may be able to install an appropriate version of Python, or you can follow the traditional Unix installation process to build Python from source.
The special build configuration variables listed above make it possible to use a regular Win32 build of bjam to build and test Boost.Python and Boost.Python extensions using Cygwin GCC and targeting a Cygwin build of Python.
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 Installing Python
Modules to create
corresponds to the major and minor version numbers of your Python
The build process will create a
libs/python/build/bin-stage subdirectory of the boost root
$(ALL_LOCATE_TARGET), if you have set that variable),
containing the built libraries. The libraries are actually built to
unique directories for each toolset and variant elsewhere in the
filesystem, and copied to the
bin-stage directory as a
convenience, so if you build with multiple toolsets at once, the product
of later toolsets will overwrite that of earlier toolsets in
To build and test Boost.Python, start from the
libs/python/test directory and invoke
This will update all of the Boost.Python v1 test and example targets. The tests are relatively quiet by default. To get more-verbose output, you might trybjam -sTOOLS=toolset test
which will print each test's Python code with the expected output as it passes.bjam -sTOOLS=toolset -sPYTHON_TEST_ARGS=-v test
-n" option so you can see the command-lines it uses, and replicate them. You are likely to run into compilation or linking problems otherwise. The
libs/python/examplesubdirectory of your boost installation contains a small example which builds and tests two extensions. To build your own extensions copy the example subproject and make the following two edits:
boost-build.jam- edit the line which reads
so that the path refers to theboost-build ../../../tools/build/v1 ;
tools/build/v1subdirectory of your Boost installation.
Jamrules- edit the line which reads
so that the path refers to the root directory of your Boost installation.path-global BOOST_ROOT : ../../.. ;
The instructions above for testing Boost.Python apply equally to your new extension modules in this subproject.
debug(no optimization -D_DEBUG)
debug-python(no optimization, -D_DEBUG -DBOOST_DEBUG_PYTHON)
The first two variants of the
boost_python library are
built by default, and are compatible with the default Python
debug-python variant corresponds to a
specially-built debugging version of Python. On Unix platforms, this
python is 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 C++ 6.0 project in the
PCBuild subdirectory of your
Python distribution. Extension modules built with Python debugging
enabled are not link-compatible with a non-debug build of Python.
Since few people actually have a debug build of Python (it doesn't come
with the standard distribution), the normal
builds modules which are compatible with ordinary Python.
On many windows compilers, when extension modules are built with
-D_DEBUG, Python defaults to force linking with a special
debugging version of the Python DLL. Since this debug DLL isn't supplied
with the default Python installation for Windows, Boost.Python uses
to temporarily undefine _DEBUG when Python.h is
#included - unless
If you want the extra runtime checks available with the debugging
version of the library, #define BOOST_DEBUG_PYTHON to re-enable
python debuggin, and link with the
debug-python variant of
If you do not #define BOOST_DEBUG_PYTHON, be sure that any
source files in your extension module #include <boost/python/detail/wrap_python.hpp>
instead of the usual Python.h, or you will have link
For the those of you who feel more comfortable in the IDE world, a
workspace and project file have been included in the libs/python/build/VisualStudio subdirectory.
It builds release and debug versions of the Boost.Python libraries and
places them and the same directory as Jamfile build does, though the
intermediate object files are placed in a different directory. The files
have been created using Microsoft Visual C++ version 6, but they should
work for later versions as well. You will need to tell the IDE where to
find the Python
Under Tools>Options>Directories, add an entry for the Python
include dir (i.e.
c:/Python22/Include), and one for the Lib
c:/Python/Libs. Make sure it is
s" and not just
Building your own projects using the IDE is slightly more complicated. Firstly, you need to make sure that the project you create as the right kind. It should be a "Win32 Dynamic-Link Library". The default one that Visual Studio 6 creates needs some modifications: turn on RTTI, and change the debug and release builds to use the respective debug and release Multithreaded DLL versions. You should probably turn off incremental linking too -- I believe it a bit flaky. If you do this, then change the "Debug Info" to "Program Database" to get rid of the Edit and Continue warning.
You'll need to add the Boost root directory under
Tools>Options>Directories to get your code compiling. To
make it link, add the above
boost_python.dsp file to your
workspace, and make your project depend upon it (under
Project>Dependencies). You should be able to build now.
Lastly, go to the Project Settings>Debug Page and add the
Python.exe as the executable for the project. Set a startup
directory, and make sure that your current project's output dll, the
boost_python.dll and the
python22.dll are on
PATH. If you have a python script that tests
your dll, then add it in the "Program Arguments". Now, if all went well,
you should be able to hit the Run (F5) button, and debug your code.
The Visual Studio project files are graciously contributed and maintained by Brett Calcott.
© Copyright David Abrahams 2002. Permission to copy, use, modify, sell and distribute this document is granted provided this copyright notice appears in all copies. This document is provided ``as is'' without express or implied warranty, and with no claim as to its suitability for any purpose.
Updated: 29 December, 2002 (David Abrahams)