From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-01-29 10:30:15
David Abrahams wrote:
> > > 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 project 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.
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.
> > > 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?
I was not sure these cases cover all possible usages, but cannot suggest any
example that is not covered.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk