6 Nov 2001 00:51
A few extensions to Jam
Craig McPheeters <cmcpheeters <at> aw.sgi.com>
2001-11-05 23:51:51 GMT
2001-11-05 23:51:51 GMT
Hi, Some of the development groups at Alias|Wavefront have been using a minor variant of Jam for a couple years with great success. We are using Jam to build large products on multiple platforms. Like most users of Jam, we have customized a local Jambase quite heavily. Along with the Jambase customizations, we have extended Jam itself in a variety of ways. The extensions to Jam may be useful for other groups working with large projects, this mail announces the availability of the extensions. Hopefully some of these will make their way into the Jam mainline. I have a branch on the Perforce public depot at: //guest/craig_mcpheeters/jam/src/... That branch now contains all of the changes we have made to Jam, in a form that is hopefully usable by a variety of people. There are 12 independent extensions, and a few simple fixes. There is a file in the branch called Jamfile.config which lists the extensions in some detail. Briefly, they are: * a header cache. Jam normally scans all source files for headers at each run. This can be time consuming on large source trees. The header cache saves the results of the current header scan, and it is re-used the next time jam is run. This can save several minutes of startup time on large projects * the output from a run of Jam using several jobs is now optionally serialized * enable command buffers to grow dynamically. Some platforms are able to accept multi-megabyte command buffers. With this extension, jam can generate(Continue reading)
Alan Burlison
) examples ?
greetings
Achim
RSS Feed