Re: [jamboost] (sub)project handling

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-12-04 17:12:28

Please leave a space between quoted text and your replies, or I am likely to
miss something important.

> > It seems to me that the Jamrules file in every project's root (which is
> > read upon invocation of Jam from every subproject) would have to give
all
> > of the subproject aliases. Would that solve most of these problems?

> Likely. How Jamfile location will be specified then? Using one-argument
> "project" (don't like such reuse, actually), or with "subproject", or... ?

Why don't you make a proposal? subproject sounds OK to me.

> Just for the record, there are some things I'd like from mutli-project
> builds, which become more important if project aliases are used instead of
> path names.
> 1. Project should be able to export include pathes, library pathes etc, so
> that user don't have to specify include path inside external project.

Yes!

> 2. Support for binaries export is also desirable. I mean something like
> GenFile foo : bar : <bin>some_toolset/sometool ;
> (frankly, don't remember exact GenFile semantics, but idea is clear
anyway)
> This might look similar to toolset mechanism but is not:
> - the external tools might not be standard, it is desirable to just untar
> and build it out of box.
> - the tools might be under development themself: so you'd need rebuild of
a
> project when used tool changed.

Yes. And finally, you probably only need one copy of the tool, rather than
one for each compiler you're build/test-ing with.

It would help if you could propose some syntax for what these features would
look like to a user.

-Dave