Subject: [Boost-build] Boost-python-based extensions using system configured with prebuilt boost packages
From: Justin Muncaster (jmuncaster_at_[hidden])
Date: 2009-08-21 14:10:55
I've looked over the documentation for boost-python and it appears that the
examples assume the user has downloaded the boost source tarball and
extracted it somewhere. On our systems we prefer to install boost-build,
boost-dev, and bjam packages our Linux distribution's package manager (in my
case, Ubuntu 9.04).
The boost-build system files are located to:
And boost includes are located to:
And boost binaries are located to:
I modify site-config.jam to pointto boost binaries as I need them. E.g.,
lib boost_thread-mt ;
lib boost_python-mt ;
while the boost headers are automatically included my path due to their
The quickstart does not work for me because to my understanding it tries to
point a 'boost' target to '../../../..', assuming that the boost source tree
is located there.
My questions are,
1. Can I build boost.python-based extensions under this configuration? If
2. Is there a better way to set things up, given the constraint that we
prefer to download boost packages using our package manager?
Thanks for your help,
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk