Great! Actually, I had something similar to the first part of Tom Troney's
method. The difference is I put all the dependencies in a single file
(actually two, one for the current make run and one for the 'next' make
run); all the $(MAKEDEPEND)-equivalent invocations (using GCC invoked once
instead of twice) appended info to the 'next run' file, and a Perl script
merges the two files every time make is run (using just a $(shell ...)
call). The perl script does all the munging once per make invocation so
there's no sed call for each file compiled.
The part I didn't know about was how to use targets with no dependencies or
rules. That's what I needed. So the feature I requested:
main.o : --ignore-- main.c file1.h file2.h
does exist and is written as:
main.o : main.c file1.h file2.h
main.c :
file1.h :
file2.h :
Thanks!
-Marc
> -----Original Message-----
> From: Paul D. Smith [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 10, 2000 06:16
> To: Marc E. Gauthier
> Cc: [EMAIL PROTECTED]
> Subject: Re: auto-dependencies and deleted files
>
>
> The best thing to do is avoid that method of dependency generation
> altogether. Not only does it have the problems you describe, but it's
> not the most efficient method, either.
>
> Certainly I don't think it's worth adding that special feature just to
> work around this issue; changing to a better method of dependency
> generation solves the problem more generically without it anyway.
>
> See here:
>
> http://www.ultranet.com/~pauld/gmake/autodep.html
>
> Have fun!
>
> --
> ------------------------------------------------------------------
> -------------
> Paul D. Smith <[EMAIL PROTECTED]> Network
> Management Development
> "Please remain calm...I may be mad, but I am a professional."
> --Mad Scientist
> ------------------------------------------------------------------
> -------------
> These are my opinions---Nortel Networks takes no
> responsibility for them.
