Xref: utzoo comp.sources.d:4493 alt.sources.d:410
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.dal.ca!silvert
From: silvert@cs.dal.ca (Bill Silvert)
Newsgroups: comp.sources.d,alt.sources.d
Subject: Re: Looking for a make version to better support software versions
Summary: can be done with present make
Message-ID: <1989Dec29.133013.17153@cs.dal.ca>
Date: 29 Dec 89 13:30:13 GMT
References: <1440@jimi.cs.unlv.edu>
Sender: silvert@cs.dal.ca.UUCP (Bill Silvert)
Reply-To: bill@biomel.UUCP
Organization: Habitat Ecology Div., Bedford Inst. of Oceanography
Lines: 20

In article <1440@jimi.cs.unlv.edu> jack@jimi.cs.unlv.edu (Jack Alexander) writes:
>I have a need for a make-type program that will allow recompilations
>to be dependent on the changing of compiler definitions (i.e., "-DVERSIONB")
>... However, when I change
>a compile variable, I don't want to re-compile every file (some directories may
>have 50 source files each), just the ones that actually reference the variable.

It seems that this should be doable with existing forms of make.
Arrange to set each define in a file (use `cat ...` to get the contents
into the command line) and set up dependencies.  Then when you edit the
file "versionb" (containing just the line "-DVERSIONB") the appropriate
files get remade.  The dependencies can be set up either by hacking an
existing dependency generator or by using greps.


-- 
Bill Silvert, Habitat Ecology Division.
Bedford Institute of Oceanography, Dartmouth, NS, Canada B2Y 4A2
	UUCP: ...!{uunet,watmath}!dalcs!biomel!bill
	Internet: biomel@cs.dal.CA	BITNET: bs%dalcs@dalac.BITNET