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

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

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

> David Abrahams wrote:
>
> > > David Abrahams wrote:
> > > > 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.
> > >
> > > Good point. On the other hand, suppose some other module (not
> > > project-root/Jamfile) would like to make some rule available in
Jamfile
> > > without qualification. I suppose there should be way to do it, and a
rule
> > > in project module seems like the right way.
>
> > This sounds like premature generalization to me. Can you envision a need
> > for this capability?
>
> For example, rules like "exe" are better used unqualified, and module that
> declares them will need the ability to inject then in Jamfiles.

I always thought that the really common rules would be explicitly exported
to the global namespace without qualification so they'd be available
everywhere. For more esoteric rules, I don't mind the idea that a user
writes:

python.extension my_extension_module : ... ;

or

import python : extension ;
extension my_extension_module : ... ;

etc.