Re: [Boost-build] Effect of usage requirements vs. default values of a feature

Subject: Re: [Boost-build] Effect of usage requirements vs. default values of a feature
From: Gevorg Voskanyan (v_gevorg_at_[hidden])
Date: 2011-04-16 13:29:56

Steven Watanabe wrote:
> Unfortunately, you aren't allowed to  put
> non-free features in usage-requirements.
> I'd like it to work, but I'm  not sure how
> to specify exactly what the behavior should
> be in all  cases.

Thanks Steven, that really is unfortunate. The doc doesn't mention this 
limitation IIRC.
I can see these complicating factors:
1. Which source alternatives get selected depends on values of non-free features 
in requirements
2. Conditional requirements in usage-requirements where produced property's 
feature is non-free
Do you see other problems which need to be thought about?

Thanks very much,
Gevorg