Re: Run target dependency on exe without getting transitive usage requirements

Steven Watanabe via Boost-build <[email protected]> Mon, 11 Mar 2019 13:00:56 -0600
Newsgroups gmane.comp.lib.boost.build
Organization Providere Consulting, Inc.
Message-ID <[email protected]>
AMDG

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 ;

In Christ,
Steven Watanabe
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build