From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-04-18 09:14:40
----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
> > > There's also one interface question not addressed yet. I'd like to
> > > implement almost full project support for the first milestone. We
> > > need an ability to load other project's project-root.jam, so that
> > > file could forward declare project id that will be used later.
> > > syntax? Something like:
> > > use-project /path/to/my/project ;
> > I think we defined some syntax in
> > ld_Projects, but I'm not certain that we concluded our discussion.
> > it moved to the jamboost list?
> We've discussed slightly different thing, namely how to associate
> with project location. Suppose I have a big external library. I could
> 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
> changes? What I want is:
> use-project $(BIG_LIB) ;
> That should load project-root.jam located at $(BIG_LIB), which will
> all project ids that might be of interest to users.
Isn't that simply:
project big_lib : $(BIG_LIB) ;
> Actually, there's a
> terrible confusion with the 'project' root. We'd need a word to denote
> 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.
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