 |
This article needs additional citations for verification. Please help improve this articlebyadding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Perforce Jam" – news · newspapers · books · scholar · JSTOR (November 2017) (Learn how and when to remove this message) |
| Original author(s) | Christopher Seiwald |
|---|---|
| Final release | 2.6 / August 7, 2014; 9 years ago (2014-08-07) |
| Written in | C |
| Operating system | Cross-platform |
| Type | Software development tools |
| License | open-source |
| Website | www |
Perforce Jam was an open-source build system developed by Christopher Seiwald of Perforce Software. It was used as a replacement for make. Its primary feature was its ability to express build patterns in an imperative language which supported structured namespaces (similar to Pascal records) and simple lists. Jam could be used with autoconf, although it was often not necessary because of Jam's portability features. Perforce Jam ran on Unix (including many clones), OpenVMS, Windows NT (including Windows 2000 and Windows XP), Mac OS, and BeOS. It was also possible to configure it to work on Windows 9x using MinGWorCygwin.
The company announced that version 2.6 released in August 2014 was the last Perforce Jam release.[1]
FT Jam is a popular variant and fully backward compatible, although its features are being integrated into Perforce Jam. Users of FT Jam often refer to Perforce Jam as "Classic Jam".
The Boost C++ Libraries is using a Jam variant called "Boost.Jam" (or "BJam"). It is incompatible with other variants, and is not a standalone tool, but part of Boost.Build.
Haiku Jam is a custom fork of Perforce's Jam used by Haiku.
JamPlus adds new features to Jam and integrates a number of patches from the Jamming mailing list and the Perforce Public Depot.
Jam comes with a set of rules called "Jambase", which define rules for building various things. Jambase is "smart" and knows, for instance, that if a header file is modified, all files that include it must be rebuilt. Unlike with makefiles, the writer of the Jamfile need not manage these dependencies, only list the source code files themselves. Jambase is usually compiled into the executable file itself.
Jambase is notorious[citation needed] among Jam users for its bugs and the infrequency with which fixes are integrated into the distribution, though few bugs are critical. There are some packages such as AutoJam designed to solve some of the problems of Jambase.
