Re: [jamboost] QT support, and some problems

From: Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2003-01-20 16:12:34

Am Montag 20 Januar 2003 14:15 schrieb Vladimir Prus:

> The current situation is:
> 1. All libraries are shared by default
> 2. -rpath is not passed
>
> However, there's "hardcode-dll-paths" property. When it's set, for
> each linked executable, paths for each library is added to -rpath.
> For example, if you go to examples-v2/libraries and run
>
> bjam hardcode-dll-paths=true
>
> there, then you'll be able to run
>
> app/bin/gcc/debug/main-target-app/app
>
> without adjusting LD_LIBRARY_PATH.

Well, I've converted one build from qmake to bjam. It took 45 minutes 
and worked fine. The problem with <hardcode-dll-paths> seems to be that 
it only hardcodes user.specified libraries following the "exe : " rule.
The qt is not hardcoded. 

Is there any reason why I have to specify the "lib" prefix on unix 
libraries in v2 ? V1 did this by automatic, so declaring libfoo was 
done by writing: "lib foo :" Now I have to write "lib libfoo :" which 
is extra work and leeds to confusion when building on win32, where you 
have the ".lib" postfix...

I'll take a try on external libs tomorrow.

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de