[Boost-build] Or-matching for alternatives (Was: ** Need input on alternative selection **)

From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-04-25 12:11:01

On Wednesday 18 April 2007 10:13, David Abrahams wrote:

> > 2. You claim that it's often desirable to express
> > "select this alternative is either <feature1>value1 or ... 
> > ... or <featureN>valueN" is in properties.
> 
> Yes, especially in the presence of prebuilt libs.

Okay, this claim is clear and indeed it's not possible to express
"select this alternative is either <feature1>value1 OR .... OR <featureN>valueN
is in requirements".

However, I still at loss what real examples call for this behaviour. Would
you mind providing some?

- Volodya