Re: [bug-gnulib] using AC_LIBSOURCES: complementing the `Files:' section

[Jim Meyering]

Bruno Haible <address@hidden> wrote:
> In gnulib we achieve this through the
>
>   lib_SOURCES += mempcpy.h
>
> line in the modules description file.

I am well aware of that practice, and it's great that
gnulib-tool can use that information.

> I don't understand the philosophy of registering filenames through
> autoconf macros. I thought lists of filenames and compilation rules and
> flags belong in Makefile.am, and stuff that is needed for "configure"
> belongs in autoconf macros.

This philosophy is nothing new, just not as widespread as it should be.
It's been done for obstack and error via their AC_ macros for ages.
I wish we had adopted the practice sooner.

Isn't it more in the spirit of autoconf and automake to use their built-in
capabilities to perform this small task rather than to make gnulib-tool
do it?  Then even packages (ahem :-) that don't use gnulib-tool can
benefit from that dependency information.

Besides, if I write an autoconf macro to detect and potentially
replace a function, I consider the replacement .c file (and of course
its header file) to be tightly enough coupled to the macro that it is
only logical to include their names in the definition of that macro.

Jim