On Tue, Jan 27, 2009 at 9:44 PM, willard wrote:
> this is my example (create the foo.d manually as below)
Well, now that you've shown your whole Makefile, I have a guess as to
why make is behaving as it is. It's tied that the face that you use
foo.d both as an implicit target (by virtue of being
this is my example (create the foo.d manually as below)
$ cat bad.mak
all: foo.d foo.ooo
COMPILE=gcc
%.o: %.c
$(COMPILE) -c $<
%.d: %.c
$(COMPILE) -c $< -MM -o $*.d
-include foo.d
foo.ooo: foo.o
ld -o foo.ooo foo.o
[/cygdrive/d/opentv/tstmake]
$ make -f bad.mak
make:
On Tue, Jan 27, 2009 at 8:59 PM, willard wrote:
> When using the "-include filename"(instead of just "include filename"), if
> this filename includes dependencies that are missing, makefile does not show
> those missing dependencies...
>
> For example, if using:
>
> -include foo.d
>
> with foo.d b
When using the "-include filename"(instead of just "include filename"), if
this filename includes dependencies that are missing, makefile does not show
those missing dependencies...
For example, if using:
-include foo.d
with foo.d being:
foo.o: foo.c xxx.h
Let's say xxx.h does not exist (and