l target is "a.o", make will try to build all the included
> makefiles. Then after a.d is built, make re-execs and builds the
> original goal target "a.o".
So make will always check if included targets are up to date and run them
if they are not, got it. Now it ma
related, I don't think autoremaking answers my
second question. Why does rebuilding running "make a.o" also rebuild a.d?
a.o doesn't depend on a.d.
On Wed, Sep 23, 2015 at 12:24 PM, Paul Smith wrote:
> On Wed, 2015-09-23 at 12:15 -0500, John Westing wrote:
> > So wh
So when an include make file gets modified make restarts the original make
file?
For efficiency I don't want to always create the dependencies, that's why I
did it this way. Is there anyway to disable remaking?
On Wed, Sep 23, 2015 at 12:13 PM, Paul Smith wrote:
> On Wed, 2015-09-23 at 13:06 -0
Any ideas?
On Wed, Sep 23, 2015 at 11:14 AM, John Westing wrote:
> I originally posted this problem here:
>
>
> http://stackoverflow.com/questions/32742321/make-unexpected-behavior-with-dependencies-and-include-statement
>
> Here's my problem:
>
> I have the following Ma
I originally posted this problem here:
http://stackoverflow.com/questions/32742321/make-unexpected-behavior-with-dependencies-and-include-statement
Here's my problem:
I have the following Makefile:
a.d:
gcc -m32 -MM -o $@ a.c
sed 's!a.o!$@ a.o!' --in-place $@
a.o:
