From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-04-19 03:33:57
David Abrahams wrote:
> ----- Original Message -----
> From: "Vladimir Prus" <ghost_at_[hidden]>
> > Not sure. So far, 'project' has purely declarative semantics. It would
> > prevent any project ids declares in big_lib's project-root.jam from
> > accessible to use. Or should 'project' load Jamfile in the given
> Why not? That's cheap, especially if Jamfiles are mostly declarative ;-D
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 override
that? Should both coexist?
project id : ....named arguments.... ;
declares project id for the Jamfile where that invocation appears.
> > I agree but I was not proposing anything different. Just if we have
> > project-roots how should be call (in our discussions or docs)
> > under one project-root. "top-level project"? "module"?
> 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?
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