Re: [Boost-build] rpath question with bjam building python extensions.

Subject: Re: [Boost-build] rpath question with bjam building python extensions.
From: Dave Abrahams (dave_at_[hidden])
Date: 2010-11-24 13:06:28

On Wed, Nov 24, 2010 at 5:21 AM, Simon <simon.vanmaercke_at_[hidden]> wrote:
> I want to build a python extension using bjam. The extension links to
> some libraries that are not in the default library path, including some
> boost libraries (eg. libboost-python).
>
> When trying to import the compiled module, i get complaints that python
> is unable to locate those libraries.
> After adding all directories to the LD_LIBRARY_PATH everything is fine.
>
> Now the question: why is there no "rpath" addded to the shared library
> that is created?

Because not everybody wants the location of libboost_python hardcoded
into their application.

> And what is the easiest solution to get a working
> python module without compiling statically, or creating a lot of
> symbolic links?

Set LD_LIBRARY_PATH?

Or you could add the rpath option to the link line yourself by
rebuilding your extension module with linkflags=... on the bjam
command line.

> I guess I'm missing something the size of large building
> here, but I can't find any clues.
> (boost version is 1_42_0, gcc 4.1, ubuntu 9.10)

I'm not sure you are, but I'm also not sure your expectation for an
rpath binding is universally shared.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com