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:Roesler, Randy (rroe@mdsi.bc.ca)
Date:01/03/2002 07:04:25 PM
List:com.perforce.jamming

How about ...

rule Newest { # do nothing .. just introduce a node to JAM }

action Newest { # do nothing .. just tell jam how it can build a Newest }

Newest N ;

# And then you a -> b -> c becomes

DEPEND b : a ; DEPEND c : b ;

DEPEND b : N ;

--

I have not tried this, but it is a "trick" used in make all of the time.

Since N never exists, its always forces the build of anything that depends on it.

But jam only builds thos things related to the top level target (normall all), so in c is no required by this target, it always gets built.

(An ALWAYS applied to N could not hurt !)

-----Original Message----- From: Craig McPheeters [mailto:cmcp@aw.sgi.com] Sent: Thursday, January 03, 2002 6:50 PM

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

Let's say file c depends on b which depends on a

a -> b -> c

File b is an intermediate file that, for various reasons, is best not marked TEMPORARY ...

When I run jam, I want b to always be re-built, but only in the cases where c is being built.