Subject: Re: [Boost-build] How to write such a feature?
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-09-23 03:12:52
On Tuesday 22 September 2009 Sherwood Hu wrote:
> Thanks. I followed the instruction and they worked.
> feature enable-unit-test : on off : composite propagated ;
> feature.set-default enable-unit-test : off ;
> feature.compose <enable-unit-test>on : <define>_UNIT_TEST ;
> feature enable-debug-module : on off : composite propagated ;
> feature.set-default enable-debug-module : off ;
> feature.compose <enable-debug-module>on : <define>BK_DEBUG_MODULE ;
> Now I have another question. The attribute "propagated" is quite strong
> and applies on the whole dependency tree. Is there an attribute that
> only applies to one target but stronger than what the "free" attribute
> can provide?
> Assume that my unit test exe is linked to libA, which has dependency
> libB. I want the new feature <enable-debug-module> only applies to libA
> not libB. That is, the test exe is linked to libA built with
> <enable-debug-module>on and libB built with <enable-debug-module>off.
> Is this possible?
This is not presently possible. Is propagation to libB causing you any
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