Re: Eliminating more recursive make invocations

[John W. Eaton]

On 07/13/2015 09:26 AM, John W. Eaton wrote:

> We could also use move-if-change more, but that introduces its own
> problems because then targets end up being always out of date, so you
> perform the generation step anyway, then throw away the result.  That
> isn't bad if the generation steps are fast, but it's annoying when they
> are not.

I checked in a changeset that uses move-if-change in many more rules. 
This seems to help to limit the damage if you touch the Makefile.am file 
or one of the module.mk files.

It does have the effect I described previously, but for now that doesn't 
seem too bad.  Certainly it is not as bad as remaking everything just 
because the Makefile is touched for some reason unrelated to most (or 
all) of the generated source files.

jwe