Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.sources.d
Subject: Re: Looking for a make version to better support software versions
Message-ID: <2792@auspex.auspex.com>
Date: 4 Jan 90 18:43:18 GMT
References: <1440@jimi.cs.unlv.edu> <297@digi.UUCP>
Organization: Auspex Systems, Santa Clara
Lines: 21

>Yes, go out and buy an Apollo and use DSEE.  It keeps up with not only the
>version of source that goes into making an object, but all the command(s), and
>options to the commands, as well.

Yes, and he can also buy a Sun (or, presumably, Solbourne) and, if it's
running 4.x or 3.x with the "SunPro make" he can get that as well from
"make" if he uses ".KEEP_STATE", but it's possible that he's not in a
position to throw out existing machines and cut over entirely to a new
one....

In addition, he didn't just want to have the system keep track of the
commands (which includes the options, at least in the way the Sun "make"
thinks of it) used to build an object, he wanted it to *only* remake
those modules that actually *use* the value of a #define from the
command line:

Jack>However, when I change a compile variable, I don't want to
Jack>re-compile every file (some directories may have 50 source
Jack>files each), just the ones that actually reference the variable.

which the Sun "make" won't do automatically - will DSEE do that?