[openbeos-build-team] Re: Detecting libgcc

  • From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
  • To: openbeos-build-team@xxxxxxxxxxxxx
  • Date: Sun, 30 Jun 2002 02:56:40 CEST (+0200)

> >5) fixing paths and path related issues in files (e.g. the
> > stupid SubDir and SubInclude rules in Jamfiles (I strongly 
> > recommend to
> > replace them by ones that work dir-relatively) (a little script can 
> > to
> > that)) and commiting the changes
> The SubDir and SubInclude rules take a full path simply because these 
> rules
> are used to find the Jamrules file. That file should be in the top 
> level
> directory of the build process, and to find it Jam needs to be able 
> to find
> that directory.

A Jamfile (except the one at the top level of course) simply includes 
the Jamfile in the parent directory. Once found the path to the top 
level directory is kept track of in a variable (maintained stack-like). 
That way always the whole Jamfile tree is read, which enables you to 
build a target in a subdirectory and have targets from other parts of 
the directory hierarchy it depends on updated, if necessary.
The only (?) flaw of this system is, that in a subdirectory you have to 
name the target you want to be built, otherwise the whole tree gets 

CU, Ingo

Other related posts: