Re: [Boost-build] Run target dependency on exe without getting transitive usage requirements

Subject: Re: [Boost-build] Run target dependency on exe without getting transitive usage requirements
From: stefan (stefan_at_[hidden])
Date: 2019-03-11 17:28:57

On 2019-03-11 1:24 p.m., Chambers, Matthew via Boost-build wrote:
> Did this message actually get through? This would be a nice feature to 
> have.
>
> On 11/30/2018 5:56 PM, Chambers, Matthew wrote:
>> I have a run target that needs to wait until an exe is built before 
>> it runs. When I pass it as <dependency> it adds all the exe's usage 
>> requirements (almost all of which are propagated from the exe's own 
>> lib dependencies) to the run target. How do I avoid that? Is this by 
>> design? Shouldn't depending on an exe only propagate the exe's own 
>> usage-requirements, not any transitive usage-requirements?

How do you determine whether a usage-requirement needs to propagate or 
not ? I can think of a couple of parameters that need to be propagated 
to such "run" targets. For example any settings on LD_LIBRARY_PATH (I 
believe in fact b2 injects them so you can run boost tests without 
installing all the (shared) libs first).

Stefan

--
       ...ich hab' noch einen Koffer in Berlin...