Re: [boost] build free-features

From: Thomas Witt (witt_at_[hidden])
Date: 2001-11-21 10:24:58

On Wednesday 21 November 2001 15:52, you wrote:
> ----- Original Message -----
> From: "Thomas Witt" <witt_at_[hidden]>
>
> > My problem is that direct deps can't handle our project structure very
>
> well.
>
> > It looks like this
> >
> > root/
> >    lib1/
> >       cpp/
> >    lib2/
> >       cpp/
> >    app1/
> >        cpp/
> >    app2/
> >        cpp/
> >
> > LibX are static libs that will be linked to both apps, so directory
>
> structure
>
> > cannot reflect dependencies. To improve convenience I placed redirecting
> > Jamfiles in the cpp dirs that look like this
> >
> > -------
> > subproject lib1/cpp ;
> >
> > subinclude . ;
> > ----
> >
> > As a result jam can be invoked from every project directory. With my
>
> current
>
> > emacs compile configuration this is a must.
>
> The subinclude isn't neccessary to be able to invoke Jam from a subproject
> directory. Normally, invoking jam in a subproject builds that subproject
> and the things it depends on. In a large project you typically don't want
> to invoke a full-project build from every subproject -- you need to be able
> to work on an isolated piece.

I agree. My point was not about building the complete tree but about building 
a subtree from its leaves. Where subtree and leaves refers to directory 
structure.

I typically put the source files in a subdir of the subproject directory so 
that they are seperated from the configuration files. Furthermore the headers 
go in their own dir too. So when editing files I do not know the path to the 
project Jamfile.

>
> Maybe when YOU invoke jam it builds the entire project regardless of which
> subdirectory you're in?

Yes, I actively tried to accomplish this. The project is sufficiently small 
and it's convenient for me.
  
Thomas

-- 
Dipl.-Ing. Thomas Witt
Institut fuer Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet Hannover
voice: [phone] - 4273, fax: [phone]
http://www.ive.uni-hannover.de