Re: [jamboost] The "project" rule

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-07-05 10:28:31

David Abrahams wrote:

> > I'm afraid that I don't understand you here. If project-root.jam says
> >
> > use-project boost : /home/ghost/Work/boost ;
> >
> > then you can use project-id boost. What is the meaning of
> >
> > project my : jamfile-location /home/ghost/Work/my ;
> >
> > ?
> > ("architecture.html" uses
> >
> > project.jamfile-location build
> >
> > but that's just different syntax)
>
> Good points; I agree with you. Let's just go with use-project.

And at this very momemt I'm going to change my mind.... :-) 
We must have been discussing this already but let's reiterate this for the 
last time, now that we're online at the same time.

If I use another project, like boost, it would like its project-root.jam to 
define all project id in it, and we should use jamfile-location for that:

project boost/theads : jamfile-location libs/thread.... ;
project boost/python : jamfile-location ..... ;

Alternatively, we can have a third rule: export-project :

export-project boost/threads : libs/thread/....

I'm not sure which of the variants is better -- they're functionally the 
same. I also think that jamfile in the given location should be loaded, so 
that targets defined there be available.

- Volodya