updating from jam 2.1.1 to 2.3
<Stephen.Riehm <at> varetis.de>
2001-02-07 14:08:26 GMT
we've been using a slightly modified version of jam for a few years
now, and upgrading to jam 2.3 isn't going all that well, as our
modifications are of course missing in the new version. Our
modifications were minimal, but I'ld like to know if the same
functionality is now available in the current version.
We had the following extras:
A project path ($PRJPATH) was used to refer to multiple
development trees. (ie: <build_tree>:<private_tree>:<reference_tree>)
A routine was used to split a variable on any character
(similar to perl's split() function), this was used to split
PRJPATH into a list of paths (ie: a list of TOP directories).
(I believe such splitting is now standard for environment
variables whose name ends in PATH)
A second routine was added to jam to determine the directory
name relative to one of the TOP directories in $(PRJPATH).
Since jam could be started in a directory without a Jamfile
(i.e.: the Jamfile is only in the <reference_tree>) - the
Jambase set up a SEARCH for $(RELDIR)/Jamfile (SubDir thus
couldn't be used, because the Jamfile hasn't been found yet).
The effect was that a central source directory exists (the
<reference_tree>), in which the "official" code is placed. The
developers then work in a private directory (<private_tree>), again
only with source code. Finally, the developer has a third directory
(<build_tree>) where the build takes place. A complete "clean