Re: [jamboost] [V2] Problem with custom variants

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-18 07:04:32

Hi Jürgen,

> > There happen to be a bug report about such situation:
> >
> > http://localhost:7814/scarab/issues/id/BB57
> >
> > In short, if you have 'use-project' before 'project' and
> > 'use-project' refers to a child project, then child project is loaded
> > before parent, and does not inherit any settings specified in
> > 'project' rule invocation.
> >
> > I've fixed this by delaying loading of project referred by
> > "use-project". But in your case you implicitly relied on the fact
> > that 'use-project' immediately loads the referenced project.
>
> Well, I think that this bug was from me, too ;-))

Yea. 

> > I think putting variant definition into project-root.jam is safer.
> > Of, you can create a Jamfile in parent directory of "a" and "b" and
> > define the variant there, it should work as well.
>
> Well, of course. But then its out of version control. Not good for me.
> And of course I can't redefine it in project b.
>
> *sigh*
>
> I'll have to think a little more about this.

You can get almost the same effect by creating "my_variant.jam" in project a, 
and then importing it from project a and project b. The "import" rule will 
immediately load the references file, and since it will be just module, not 
Jamfile, there won't be any problems with Jamfile loading order.

> Looks like I have to try out Scarab again and take a look at the
> remaining issues before they bite my again...

This might be a good idea, though the list of growing shorter and shorter ;-)

- Volodya