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: ()
Date:01/04/2002 03:08:17 PM
List:com.perforce.jamming

I think that with the use of the rule indirection feature which allows rules to be invoked through variable expansions,

$(rule-name) x y : z ;

you can wrap up all the logic in one place and avoid the maintenance problems. I did a similar thing for response-file support in Boost.Build.

The code to implement the feature in Boost.Jam is pretty straightforward. Let me know if you want to see it.

-Dave

----- Original Message ----- From: "Matt Armstrong" <matt+jamm@lickey.com>

Yes, this works. I'm not particularly eager to implement it in my situation though -- there are 3-4 of these temporary files (scripts, linker definition files, various response files, etc.) and passing all of them along as the targets to the various rules that create each one could be a maintenance program.

I'd be nicest to be able to write rules "normally" but have the right thing happen. Hmm...