Re: [v1] Defines not propagated to dependencies?

From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2005-08-04 11:05:47

Vladimir Prus wrote:

Note: I'm resending this because my first post seems to have ended up in 
the void somehow...

> On Thursday 04 August 2005 12:06, Markus Schöpflin wrote:
> 
>>David Abrahams wrote:
>>
>>>Markus Schöpflin <markus.schoepflin_at_[hidden]> writes:
>>>
>>>>To my big surprise, I just discovered that defines are somehow not
>>>>propagated to dependencies, when using bbv1.
>>>
>>>Right. That's the way free features work.
>>>Feature, not bug ;-)
>>
>>Thought so. But how am I supposed to build a full project where a define is
>>propagated to everything built? If you're asking for a use case: build
>>boost with -DBOOST_DETECT_OUTDATED_WORKAROUNDS.
> 
> Excellent question ;-) Maybe building from top-level will help?

I did build from libs/test/test and was wondering that libs/test/src wasn't 
getting the macro definition. Didn't try toplevel, though.

> Anyway, maybe we should reconsider our position and propagate <define> 
> features to dependencies? After all, if <define> has no effect on 
> dependencies, then it's harmless, and if it has some effect on dependency, 
> maybe we should be building with the same value anyway.

I'm +1 on this.

Markus