From: David Abrahams (dave_at_[hidden])
Date: 2004-07-02 08:12:56
Vladimir Prus <ghost_at_[hidden]> writes:
> pal.tw wrote:
>> > which would be used like:
>> > use-property <os>NT ;
>> > and will make NT a valid value of the <os> feature. If <os>NT is
>> Sorry, forgot to mention one thing...
>> How about introducing a new feature attribute, and declare those
>> features with the new attribute?
>> The new attribute might be a little like the 'free' attribute since
>> we can add one and more values, but also could be put in conditonal
>> requirements. That's what my subject means...;>
> This might work for <os>, but not the <toolset> -- since we really have to
> have only a single value from a predefined set for it. The "use-property"
> rule will have no problems with it.
An attribute still sounds like a good idea. You don't have to make
it allowable to have multiple unknown values outside of conditions.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
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