Re: [jamboost] Interaction between project-root.jam files.

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-01-29 10:12:53

----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Tuesday, January 29, 2002 10:07 AM
Subject: Re: [jamboost] Interaction between project-root.jam files.

> David Abrahams wrote:
>
> > > Since the new build system will support building multiple projects
> > > simultaneously, there comes a question of interaction between them.
> > > For example, two different project-root.jam files can declare
different
> >
> > rules
> >
> > > with the same name, to be used by Jamfiles in corresponding projects.
> >
> > That part shouldn't be a problem. Each project-root.jam should be a
module
> > (they can be distinguished with appropriate grist). Similarly, all
Jamfiles
> > should be modules.
>
> Sure, this is how I indent to make it.
>
> > If we want we can auto-import the rules from a project's
> > project-root.jam into all of its Jamfiles.
>
> In fact, I propose a rule in proejct module which will add names to the
list
> of rules that should be injected in Jamfile modules. This rule, however,
need
> to track which project-root.jam has invoked it.

I don't understand why you'd do it this way; it sounds tedious for the user.
We have module local rules and the ability to enumerate all non-local rules
using RULENAMES. We could just say that non-local rules defined in
project-root are auto-imported into the Jamfiles.

> > In general, toolset configuration (and the like) should happen in
> > user-config.jam or site-config.jam. As far as declaring new target types
is
> > concerned, I think that should be rare. We can either ask users to
qualify
> > their new target types with a project-id, or we can do it ourselves,
> > automatically.
>
> Maybe.

What's your reservation?