| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 2628 | Miklos Fazekas | Removed fix | 22 years ago | |
| #1 | 2609 | Miklos Fazekas | Branch for alternative bugfix of the deepincludes bug in 2.5rc1 | 22 years ago | |
| //guest/perforce_software/jam/src/rules.c | |||||
| #8 | 2559 | rmg | Fix 'var on target ?= value' so that var is only set if it did not have a target-specific... value. Previously, it would just overwrite the var's value. Bug fix documented in RELNOTES. === computer:1666: Change 39566 by seiwald@play-seiwald on 2002/12/27 14:44:01 « |
22 years ago | |
| #7 | 2529 | rmg | Fix "on target" variables during header scan, from Matt Armstrong. Setting target-speci...fic variables while under the influence of the target's target-specific variables caused the _global_ values to be modified. This happened both during header file scanning and with the "on target statement" syntax. The manifestation of this was if a file #included itself, HdrRule would accidentally set HDRRULE/HDRSCAN globally, and then all files (executables, etc) would get scanned for includes. While this borrows from Matt's fix, it is a slightly different implementation. User visible fix documented in RELNOTES. === computer:1666: Change 39095 by seiwald@play-seiwald on 2002/12/17 14:00:58 « |
22 years ago | |
| #6 | 2499 | rmg | Fix 'includes' support so that included files aren't treated as direct dependencies durin...g the command execution phase. If an included file failed to build, make1() would bypass the including file. Now make0() appends each child's 'includes' onto its own 'depends' list, eliminating 'includes'-specific code in make0() and make1(). This not only fixes the bug, but removes some complexity as well. Bug fix documented in RELNOTES. === computer:1666: Change 38399 by seiwald@play-seiwald on 2002/12/03 16:00:40 « |
22 years ago | |
| #5 | 2493 | rmg | Rewrite the past: update all jam's source with comments to reflect changes since about 2....3, very early 2001. Whitespace only change. === computer:1666: Change 37660 by seiwald@play-seiwald on 2002/11/06 22:41:35 Note: I regenerated jamgram.c on my linux 7.3 system prior to the submit, since patch was so unhappy trying to lay down the changes from Christopher's change. Presumably this is just due to different yacc/bison/whatever particulars on the system where Christopher made the changes originally. - rmg « |
22 years ago | |
| #4 | 2491 | rmg | Some consting in jam to make it more compilable by C++ compilers. No functional change.... === computer:1666: Change 37433 by perforce@perforce on 2002/10/30 16:08:51 Recreational const-ing of jam, for compilers that don't allow "string" to be passed as a non-const char *. This included a few places where we were modifying what could possibly have been read-only storage, oddly enough. No functional change. === computer:1666: Change 37602 by seiwald@play-seiwald on 2002/11/04 17:25:40 « |
22 years ago | |
| #3 | 2482 | rmg | Jam.html partial rewrite and the support for named parameters to rules. === computer:1...666: Change 34516 by seiwald@play-seiwald on 2002/06/21 23:59:12 « |
22 years ago | |
| #2 | 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. « |
24 years ago | |
| #1 | 2 | laura | Add Jam/MR 2.2 source | 27 years ago | |