|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-12-10 03:51:18
Rene Rivera wrote:
> [2002-11-10] Vladimir Prus wrote:
>
>
>>Rene Rivera wrote:
>>Okay.. I seem to understand this better now, thanks. One more question on
>
> topic:
>
>>is there a way to hardcode the path to shared library in exe? I want it in
>>order to avoid setting LD_LIBRARY_PATH when debugging, when libraries live
>>in build directories.
>
>
> Yes, you can, and this is what I do in my projects for debug binaries also.
> In V1 I have this set for all my targets:
>
> <gcc><linkflags>"-Wl,-rpath -Wl,."
> <gcc><linkflags>"-Wl,-rpath -Wl,$(GCC_STDLIB_DIRECTORY)"
Hmm.. I've just tried that, and not sure this is what I want. This requires
that all libraries are placed in the same directory as binary. What I wanted
is to leave all binaries and libraries in build directories, but guarantee
that dlls are found, but somehow placing *full* path to all needed dllls.
Is that possible?
- Volodya
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