18 messages in com.perforce.jamming[jamming] Expressing "lazy always upd...
FromSent OnAttachments
Matt Armstrong03 Jan 2002 16:37 
Craig McPheeters03 Jan 2002 18:49 
Roesler, Randy03 Jan 2002 19:04 
Arnt Gulbrandsen04 Jan 2002 04:39 
Matt Armstrong04 Jan 2002 14:27 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)04 Jan 2002 14:36 
Craig McPheeters04 Jan 2002 14:59 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)04 Jan 2002 15:08 
Matt Armstrong04 Jan 2002 23:48 
Matt Armstrong05 Jan 2002 00:20 
Arnt Gulbrandsen07 Jan 2002 02:33 
Matt Armstrong07 Jan 2002 09:16 
Craig McPheeters07 Jan 2002 13:28 
Craig McPheeters07 Jan 2002 13:57 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)11 Jan 2002 15:18 
Matt Armstrong11 Jan 2002 16:15 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)11 Jan 2002 16:40 
Lex Spoon12 Jan 2002 07:48 
Subject:[jamming] Expressing "lazy always update" intermediate files
From:Matt Armstrong (matt@lickey.com)
Date:01/07/2002 09:16:57 AM
List:com.perforce.jamming

Arnt Gulbrandsen <ar@gulbrandsen.priv.no> writes:

Matt Armstrong <matt+jamm@lickey.com>

Doing it in a single action is impractical due to the limitations of my shell (Win NT cmd.exe).

If you don't mind a bit of topic drift, I'm curious about that. Could you describe what would happen?

Actually I don't think it is NT specific -- these "response files" are huge, so they must be built with piecemeal actions. So, it isn't possible to build all the response files with a single actions block.

Craig showed me how to build multiple targets by putting all of them in $(<), but I think that gets too complex.

multiple-targets targetA targetB targetC : ... ;