Some examples for the use of boost::python
These are a few examples on how to use the boost::python library to extend Python with C++ libraries. Some of the are based on the existing tutorial for boost::python from Joel de Guzman. Others are independent.
The examples should work on Linux, Windows and OSX, but currently have not been tested much under Windows.
There is a special package needed called boost-python. The standard boost package will not be recognized by cmake.
brew install cmake boost-python
Furthermore, for the homebrew python lib to be used, its path must be provided to cmake. This is handled in the build.sh
script, but for reference, or if any issues arise, that can be done manually as follows (substitute the path as appropriate for your Python version):
cmake -DPYTHON_LIBRARY=/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib ..
BOOST_ROOT
environment variable if Boost is installed in a non-standard directorymkdir build ; cd build
cmake ..
and afterwards make
Alternatively, run the provided build.sh
script.
All examples contain tests, but these only try to run the examples without checking the output. Their purpose is mainly to make sure that compilation works and produces valid Python modules.
The code works with Python 3 both on Linux and on OS X. However, there are several caveats.
python
resolves to python3 (e.g., by using a python3 VE)./build.sh
Some effort has been made to make Python 3 compilation automatic, by making modifications to build.sh
and CMakeLists.txt
that account for quirks on the Apple platform regarding cmake, paths, and naming conventions for python/python3. Having said that, if you use build.sh
, then you will still need to do the following:
brew install boost-python3
python
resolves to python3 (e.g., by using virtualenv)cmake
uses matching python interpreter and libraries (down to the last digit). Otherwise you run into #17.If you are building without build.sh
, then you will additionally need to:
cmake -DBOOST_LIBRARYDIR=xxx -DPYTHON_LIBRARY=xxx -DPYTHON_INCLUDE_DIR=xxx ..
Contributions are very welcome. The following will provide some helpful guidelines.
If you want to submit a contribution, please follow the following workflow:
Commit messages should be clear and fully elaborate the context and the reason of a change. If your commit refers to an issue, please post-fix it with the issue number, e.g.
Issue: #123
Furthermore, commits should be signed (git commit -s
) according to the DCO.
If your Pull Request resolves an issue, please add a respective line to the end, like
Resolves #123