/* Keep JAMVERSYM in sync with VERSION. */ /* It can be accessed as $(JAMVERSION) in the Jamfile. */ #define VERSION "2.5rc2" #define JAMVERSYM "JAMVERSION=2.5"
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 2629 | Miklos Fazekas | Sync to 2.5 rc2 | ||
| #1 | 2522 | Miklos Fazekas | Graphisoft bugfix jam | ||
| //guest/perforce_software/jam/src/patchlevel.h | |||||
| #15 | 2513 | rmg |
Set the version number and patchlevel for the 2.5rc1 release. In RELNOTES, don't document the different behavior when a "return" is not the last statement executed in rule definition as a non-backward-compatible change (in the "Compatibility" section). |
||
| #14 | 2496 | rmg |
Fix SubInclude's error message so that it actually mentions the variable that is unset. Also bumped patchlevel to 2.4.2 capriciously. Change to unreleased behavior. === computer:1666: Change 38182 by seiwald@tricks-seiwald on 2002/11/25 10:47:50 |
||
| #13 | 2484 | rmg |
Rework make0() to consider headers when deciding whether to update a temporary source file. This makes it possible to have generated, temporary source files that must be regened because an included header has been updated. === computer:1666: Change 35018 by seiwald@play-seiwald on 2002/07/17 10:41:35 Followon to 35018: actually update a "needtmp" target (duh). === computer:1666: Change 35023 by seiwald@play-seiwald on 2002/07/17 11:10:16 Fix to 35018, which handled out-of-date header files built from temporary sources. Unfortunately, the change made circular header dependencies (which are legion) get reported. Now the circular dependency reporting is done in the call to make0() rather than at the beginning of make0(), and step 3b (the header recursion) simply skips that check. Change to unreleased behavior. === computer:1666: Change 36247 by seiwald@waffle-cyg-seiwald on 2002/09/16 16:15:10 |
||
| #12 | 1658 | rmg | 2.4rc2 becomes 2.4 (final). | ||
| #11 | 1617 | rmg | Branding 2.4rc2 | ||
| #10 | 1593 | rmg | Branding this "2.4rc1". | ||
| #9 | 1580 | rmg |
Changes for 2.4beta. Yes, Christopher, I brashly said "2.4-dev WAS the beta" at tea yesterday, but I've since come to my better instincts (got chicken?), so this one will say rmg $ jam -v Jam 2.4beta. OS=LINUX. Copyright 1993-2002 Christopher Seiwald. for a week or two, at least. |
||
| #8 | 1319 | rmg |
Jam 2.3 + Perforce's internal changes. This change is a drop of the Perforce internal Jam changes since the 2.3 public release. The individual changes represented herein are preserved in the //guest/richard_geiger/intjam/ branch. The intent of this drop is to provide a base, from which other contributors' Jam branches may be integrated into. It is not intended to become a packaged release in this state. We will be integrating changes from other users prior to creating the next packaged release. Please refer to the src/RELNOTES file for an overview of the changes present in this integration. - Richard Geiger Open Source Engineer at Perforce |
||
| #7 | 556 | Perforce staff |
Patch release jam 2.3.2: reverse NOCARE change. NOCARE once again applies to targets with source and/or actions, so that buildable header files get built. |
||
| #6 | 486 | Perforce staff |
Jam 2.3. See RELNOTES for a list of changes from 2.2.x. Just about every source file was touched when jam got ANSI-fied. |
||
| #5 | 76 | Laura Wingerd |
Integrate command-block-too-long fix, plus minor doc updates. Jam/MR release level is now 2.2.5. (change 72, change 73, change 74, change 75) |
||
| #4 | 5 | Perforce maintenance | Jam/MR 2.2.4 (HDRPATTERN, JAMUNAME, JAMSHELL, plus misc tweaks) | ||
| #3 | 4 | Perforce maintenance | Jam/MR 2.2.2 (AmigaOS support) | ||
| #2 | 3 | Perforce maintenance | Jam/MR 2.2.1 (fix for NT handle leak) | ||
| #1 | 2 | laura | Add Jam/MR 2.2 source | ||