in target's usage requirements?

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.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Friday 10 March 2006 00:06, Jarda Gresula wrote:
> 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?

I believe it's a bug. Can you file this on

   https://zigzag.c
s.msu.su/boost.build

so that I can look into this as soon as C++ Boost switch
work is over?

Thanks,
Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build