Re: [Boost-build] Boost-python-based extensions using system configured with prebuilt boost packages

Subject: Re: [Boost-build] Boost-python-based extensions using system configured with prebuilt boost packages
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-08-25 02:19:50

On Friday 21 August 2009 Justin Muncaster wrote:

> Hello,
> 
> 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:
>   /usr/share/boost-build
> 
> And boost includes are located to:
>   /usr/include/boost
> 
> And boost binaries are located to:
>   /usr/lib/
> 
> 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
> installed location.
> 
> 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
> so, how?

Justin,

I think you should be able to use python extensions, by modifying
the getting started to link to Boost.Python to refer to Boost.Python
library as a searched library.

Note that Boost.Build included in Ubuntu might be old, and therefore
you might want to grab a copy from Boost SVN, or from
http://boost.org/boost-build2, the nightly build link.

- Volodya