[Boost-build] <conditional> in target's usage requirements?

From: Jarda Gresula (jgresula_at_[hidden])
Date: 2006-03-09 16:06:03

It seems that the <conditional> feature is handled differently when placed to
target's requirements and target's usage requirements. 

lib a : a.cpp : : : <conditional>@platform-include-dir ;
exe b : b.cpp a ;

When the target 'b' is being built the usage requirements of target 'a' are not
applied. Actually it looks like that the platform-include-dir rule is not
invoked at all.

Is this a bug or there is some reason why it can't behave in the same way as
when placed to target's requirements?

Thanks,
Jarda.