|
Boost-Build : |
From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-02-23 16:04:33
[2003-02-21] Vladimir Prus wrote:
>
>Just FYI, it appears I need better "stage" rule before Rene has the time to
work on it.
>In brief, I need
>
> stage wi
> : {some target}
> : <location>{some system location}/bin <dll-path>{some system
location}/lib
> ;
>
>The point is that I want to install binaries and hardcode path to dynamic
libraries to
>them.
>Sure, the stage rule has to relink binaries to put new rpath. I've took the
shortest
>route,
>and made "stage" always relink executables.
Are you relinking straight to the stage location, or relinking and then
copying? The ofrmer is the ideal, but the later is what is implemented in
V1. It was just too complicated/hard to do the ideal in V1.
>At the moment the minimum functionality works --- the installed binaries
pick the
>correct
>libraries. But there's a question: what properties should be used when
relinking.
>
>Specifically: there are some properties when building "wi". Staged targets
are build
>with
>propagated properties. If we relink with the same properties, then free
<dll-path>
>property
>won't have any effect. Now, I just add free properties from stage to
original properties
>on the link action. I wonder
>
>1. Is this right?
Seems right to me.
>2. What does V1 do?
It tries, don't remember how well it succeeds, to do the same.
By the way... it will probably be easier to write the stage rule once the
modifier stuff I posted is in better working order. For eaxmple to stage
with relink to the stage location is matter of generating the new target
(with additional properties) and modfy it to build (locate) at the stage
location.
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq
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