[Boost-build] Using hardcode-dll-paths on Boost

Subject: [Boost-build] Using hardcode-dll-paths on Boost
From: Martin Baute (solar_at_[hidden])
Date: 2010-08-23 06:01:21

Sorry, I know this is most likely a RTFM question, but I did Read
whatever part of The Fine Manual I thought could be relevant, and
I did Google to the best of my ability...

I have to install Boost in a non-system location. I originally used:

$ ./bootstrap.sh --prefix=/path/to/boost --with-toolset=gcc
--with-icu=/path/to/icu --without-libraries=python
$ ./bjam -q -j8
$ ./bjam -q install

When I check the resulting libraries:

$ ldd /path/to/boost/lib/*.so

I get lots of "not found" for both the ICU libs and Boost libs
themselves.

I tried:

$ ./bjam -q -j8 hardcode-dll-paths=true

I also tried:

$ LD_RUN_PATH:/path/to/icu/lib:/path/to/boost/lib ./bjam -q -j8

I also tried some more experimental stuff like 

$ ./bjam -q -j8 dll-path=/path/to/icu/lib

but none of this worked.

I find many references on how to use dll-path and hardcode-dll-path
*while writing your own JAM files*, but I fail to find how to hardcode
the library search path into the *Boost* libraries themselves.

Yes I know I'm probably stupid. That doesn't mean I wouldn't appreciate
help here...

Regards,
--
Martin Baute