Subject: Re: [Boost-build] Run target dependency on exe without getting transitive usage requirements
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2019-03-11 19:00:56
On 3/11/19 12:44 PM, Chambers, Matthew via Boost-build wrote:
> On 3/11/2019 1:41 PM, Steven Watanabe via Boost-build wrote:
>> The only way to prevent usage-requirements from propagating
>> upwards is to create a custom target class that filters them
>> out.Â In this particular case, you can probably work around it
>> by building the run target's executable separately.
>> run a.cpp ; -> exe a : a.cpp ; run a ;
> How does this work? What prevents 'a' from running before 'a' is built?
I messed up the target names above. It should be:
exe a.exe : a.cpp ;
run a.exe : requirements <dependency>another_executable ;
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