From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2004-10-14 03:11:36
Vladimir Prus wrote:
> When working on Linux, the <hardcode-dll-paths>true is almost always what user
> wants. This allows to run binaries which use dynamic libraries without
> changing LD_LIBRARY_PATH or installing the libraries to system locations.
> What about making "true" value the default, and stop telling the user about
> The only case where it's not needed is when installing the binaries, so we'd
> need the "stage" rule to use <hardcode-dll-paths>false unless user has
> explicitly asked otherwise.
but won't this risk to compile everything twice (or at least link
everything twice since the hardcode-dll-path features is only of
importance to the link stage)?
If you have a jamfile that defines a library target and a stage rule,
first the library will be generated with the hardcoded paths. Next the
stage target will copy the library but requires a library without
hardcoded paths and thus requires to link the library again. This might
be unexpected behaviour too.
>From a multi-platform point of view (which bjam tries to achieve),
since harcoded paths are not available everywhere, I would not use them
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