Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ulysses!hector!ekrell
From: ekrell@hector.UUCP (Eduardo Krell)
Newsgroups: comp.unix.wizards
Subject: Re: 'nmake'
Message-ID: <11604@ulysses.homer.nj.att.com>
Date: 27 May 89 02:41:55 GMT
References: <1989@internal.Apple.COM> <11570@ulysses.homer.nj.att.com> <11598@ulysses.homer.nj.att.com> <4321@ficc.uu.net>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: ekrell@hector.UUCP (Eduardo Krell)
Organization: AT&T Bell Laboratories
Lines: 19

In article <4321@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>how do you maintain the state file in the face of
>an arbitrary number of editors, etc, capable of being used to munge a
>file without telling the state file? Or do you have to run some program to
>update the state file whenever you edit a file?

nmake stores in the state file the info it needs to determine what would
have to be recompiled next time. Things like time stamps of files, binding
of source and header files (ie, foo.h came from /usr/myinclude and bar.h
came from /project1/release2/include), command line options to cc,
etc.

The state file doesn't need to be kept up to date between nmake runs.
Next time you run nmake, it will recompile whatever needs to be recompiled
and update the state file.
    
Eduardo Krell                   AT&T Bell Laboratories, Murray Hill, NJ

UUCP: {att,decvax,ucbvax}!ulysses!ekrell  Internet: ekrell@ulysses.att.com