Re: Multiple makefiles and rules for CONFIG_HEADER and CONFIG_FILEentries

[Alexandre Duret-Lutz <duret_g at lrde dot epita dot fr>]

>>> "Sander" == Sander Niemeijer <niemeijer@science-and-technology.nl> writes:

[...]

 Sander> Now I recently discovered that automake places the
 Sander> rules to rebuild foo.h from foo.h.in (with the use of a
 Sander> stamp-h* file) in the Makefile of the directory where
 Sander> foo.h will appear if that directory has a Makefile and
 Sander> otherwise put it in the toplevel Makefile. But it won't
 Sander> put these rules in any of the other Makefiles.  Of
 Sander> course this leaves me with a problem if I change
 Sander> foo.h.in and perform a make, since for targets in my
 Sander> subdirectories that depend on foo.h make won't try to
 Sander> rebuild foo.h and thus these targets won't be rebuild
 Sander> either.

I've been bitten by this too.  I added your email to the Cc: list for PR/355.

 Sander> I would like to know whether anybody knows a way to have the foo.h.in
 Sander> -> foo.h (with appropriate stamp-h* usage) dependencies included in
 Sander> all my makefiles that contain targets with dependencies on foo.h.

No idea :(  Except handwriting these rules, of course, but that
means you must know how stamp files are numbered.

 Sander> I'm currently considering to let configure create a separate foo.h in
 Sander> each of the directories that need foo.h (through a
 Sander> AC_CONFIG_HEADERS([dir1/foo.h:inc/foo.h.in dir2/foo.h:inc/foo.h.in]),

This looks safer.

[...]
-- 
Alexandre Duret-Lutz