From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-04-22 08:20:27
----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
> David Abrahams wrote:
> > From: "Vladimir Prus" <ghost_at_[hidden]>
> > > accessible to use. Or should 'project' load Jamfile in the given
> > > location?
> > Why not? That's cheap, especially if Jamfiles are mostly declarative
> True. Then, we can agree on the following.
> project id : /some/path ;
> is used for declaring project id and loading jamfile specified there.
> What happens if Jamfile declares different project id? Should we
> that? Should both coexist?
Eventually, I'd like to be able to use it as a form of project renaming,
to deal with name conflicts. For now, I am happy to require that the
project ids match exactly.
> The syntax:
> project id : ....named arguments.... ;
> declares project id for the Jamfile where that invocation appears.
> > Does this cover it?
> > "project root" - the directory where the Jamfile for the top of a
> > project lives.
> > "project collection" - a directory containing the project roots of
> > multiple projects
> And where does "project-root.jam" live?
In the project root directory, of course.
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