[jamming] how jam handles LinkLibrary and SubInclude ?

[Ingo Weinhold]

On 2006-07-23 at 19:11:15 [+0200], Groleo Marius <groleo at gmail.com> wrote:
> On 7/23/06, Ingo Weinhold <bonefish at cs.tu-berlin.de> wrote:
[...]
> > I suppose the only reason for you to include lib/dir1 in lib/dir2 is that
> > you want to be able to cd into lib/dir2 and jam there.
> 
> If I would not include lib/dir1 in lib/dir2, then when I `jam` in lib/dir2,
> the libdir1 would be unknown to jam.

Yep, that's what I mean.

> The Haiku project
> > (http://developer.berlios.de/projects/haiku/) has a slightly modified jam
> > version (http://svn.berlios.de/viewcvs/haiku/buildtools/trunk/jam/) that
> > does always parse the whole Jamfile tree of the project. Since it creates
> > the dependencies to the pseudotargets (all, lib, exe, files, obj,...) only
> > for the targets defined in descendant dirs of the working directory jam 
> > has
> > been invoked from, a "jam all" in a subdirectory still works as expected
> > with the improvement that all of the project's target are known and all
> > dependencies are updated correctly too.
> 
> Lately i see some pathces on the list, and other mail-list subscribers 
> pointing
> to other flavors of jam. mostly retorically i wodner why jam doesn't include
> those patches/features ?

Because Perforce jam is virtually dead. There used to be a time when the 
maintainer was active on this list and a new version was released from time 
to time. But this hasn't been the case for years.

CU, Ingo