Re: [jamboost] Development plan

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-04-18 09:25:22

David Abrahams wrote:

> > We've discussed slightly different thing, namely how to associate
>
> project-id
>
> > with project location. Suppose I have a big external library. I could
>
> write
>
> > project big_lib/story_teller : $(BIG_LIB)/src/storyletter ;
> > project big_lib/chess_player : $(BIG_LIB)/src/storyteller ;
> >
> > But this requires that I know internal structure of that lib, and what
>
> if it
>
> > changes? What I want is:
> >
> > use-project $(BIG_LIB) ;
> >
> > That should load project-root.jam located at $(BIG_LIB), which will
>
> declare
>
> > all project ids that might be of interest to users.
>
> Isn't that simply:
>
> project big_lib : $(BIG_LIB) ;
>
> ??

Not sure. So far, 'project' has purely declarative semantics. It would 
prevent any project ids declares in big_lib's project-root.jam from been 
accessible to use. Or should 'project' load Jamfile in the given location?

> > Actually, there's a
> > terrible confusion with the 'project' root. We'd need a word to denote
>
> a
>
> > collection of projects with the same project root.
>
> I'm not certain of that. I don't want to restrict people to having all
> projects under a single root. Top-level project IDs should be associated
> with locations in the filesystem via the "project" rule. It should be
> possible to override these associations in user.jam and/or site.jam, in
> addition to setting them in project-root.jam.

I agree but I was not proposing anything different. Just if we have several 
project-roots how should be call (in our discussions or docs) everything 
under one project-root. "top-level project"? "module"?

- Volodya