Re: [jamboost] Development plan

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-04-18 08:56:12

David Abrahams wrote:

> > I've also comitted some tests for 'make'. It is test/m1-{01,02,03}.py
>
> and
>
> > also in directories test/m1-{01,02,03}.
>
> Cool! It's easy to understand how to use the test system from looking at
> these. What I don't get is that m1-01.py says:
>
> t.set_tree("test1")
>
> but I presume it really meant to say "m1-01" (?). 

You're right!

> BTW, line-endings in
> this directory seem to be messed up (all lines end with ^M^M^J).

Oh! Will fix that.

>
> Hint: you don't need a backslash at the end of lines where parens are
> not yet balanced, e.g. here:
>
> t.fail(t.read("bin/a.obj/yfc/debug/runtime-link-dynamic/a.obj") !=\
> ^---------not matched yet.

Thanks!

> If you're going to change the way toolsets are specified, it seems like
> a bad idea to use a new variable "TOOLSET" (formerly TOOLS). 

I would be a bad idea it it were and idea. It's just a typo :-)

> Why not use
> a nice command-line option, --toolset=... ? Death to variables on the
> command-line!

Yea!

> > There's also one interface question not addressed yet. I'd like to
> > implement almost full project support for the first milestone. We then 
> > need an ability to load other project's project-root.jam, so that that 
> > file could forward declare project id that will be used later. What 
> > syntax? Something like:
> > use-project /path/to/my/project ;
>
> I think we defined some syntax in
> http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Bui
> ld_Projects, but I'm not certain that we concluded our discussion. Was
> it moved to the jamboost list?

We've discussed slightly different thing, namely how to associate project-id 
with project location. Suppose I have a big external library. I could write

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 if it 
changes? What I want is:

use-project $(BIG_LIB) ;

That should load project-root.jam located at $(BIG_LIB), which will declare 
all project ids that might be of interest to users. Actually, there's a 
terrible confusion with the 'project' root. We'd need a word to denote a 
collection of projects with the same project root.

- Volodya