From: abingham2 (abingham_at_[hidden])
Date: 2003-10-08 15:16:50
--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> You should use something line <X>on in requirement for the second
> "feature-x-sources" alternative. Before that, you'll have to declare
> feature, too. I attach an example which does it. When I run
> only one file is compiled, and when I run
> bjam X=on
> another one is compiled as well. Is that OK?
Thanks for the help on that. I worked with what your example, and I
was able to get things working. Implementing variant aliases, however,
brought up another issue.
The alias selection method relies on a property being propagated from
the main target to the alias. However, that property is also
propagated to every other dependency of the main target. In my case,
that's a couple of libraries, all of which get a new build variant
based on that property.
So, is there any way to limit or localize the propagation of the
property? In this case, I'd like the property to only affect the alias
selection, not any of the other dependencies (for which the property
is essentially meaningless). Thanks.
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