Re: [jamboost] (sub)project handling

From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2001-11-28 10:19:24

David Abrahams wrote:

> ----- Original Message -----
> From: "Vladimir Prus" <ghost_at_[hidden]>
> 
>>Here are questions that I find important:
>>
>>1. What will be the syntax for indentifying projects
>>project foo ;
>>and then
>>subproject foo/src ; or
>>subproejct src ; or
>>project foo/src ;
>>
> 
> I have been thinking about this a bit. Should it be possible to identify a
> subproject according to something other than (strictly) the path from the
> root to the Jamfile? For example, the boost.python jamfile is in
> boost-root/libs/python/build
> 
> Shouldn't it be possible to identify that subproject as simply boost/python,
> so that from the top of boost you can do:
> 
> jam python

this would need to build _all_ python subprojects. E.g. I have multiple
test subprojects in different directories. Doing `jam test` should then
build all tests

> or
> jam boost/python

this would then be a way to specify a specific test (see above).
The slash-convention though might be confusing for windows user.

> 
> So, what about this?
> 
> project boost/python # (sub)project target id
> : libs/python/build # optional path from project root
> ;

What you are actually doing is defining an alias for the subproject.
I would seperate this from real references to the subproject 
(libs/python/build).

Maybe what is more important is to be able to specify one specific target.
For intance, when I'm in libs/regex/build, `jam libboost_regex.a` should 
build
the corresponding lib. This is usual stuff in make.