Re: [v1] Defines not propagated to dependencies?

From: Markus Schoepflin (markus.schoepflin_at_[hidden])
Date: 2005-08-04 07:36:02

--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> On Thursday 04 August 2005 12:06, Markus Schöpflin wrote:
> > David Abrahams wrote:
> > > Markus Schöpflin <markus.schoepflin_at_c...> 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 didn't try so far. I was building from libs/test/test and wondering 
why libs/test/src didn't get the macro definition.

> 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