From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-10-22 01:34:25
> The composite properties in 'requirements' attribute seems not to
> expanded to non-composite properties as the follow...
When I put <variant>release in requirements of an exe, I get pretty strange
behaviour indeed. Only the value of <variant> is changed, but things like
<optimization> and <debug-symbols> are not changed.
> Is it a limitaion that composite properties should not
> be used in requirements or just a bug?
I'd say it's a bug. Alas, I'm not sure when I'll be able to address it
though.. maybe, you could look at "basic-target.refined-properties" method in
targets.jam and see if a call to 'expand-composites' method on
'erequirements' will help? If so, you might be able to send a patch, or I'll
be able to fix this quickly when I get to work on Boost.Build.
> And I also found the 'feature.set-default' rule can't
> set the default value of a composite feature.
What precisely happens?
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