Paul Eggert <[email protected]> writes:
> While looking into this I noticed that ftoastr, like some
> but not all other modules, puts a .h file into lib_SOURCES:
>
> lib_SOURCES += ftoastr.h ftoastr.c dtoastr.c ldtoastr.c
>
> Now I naively had thought that lib_SOURCES was just for
> .c files that produce .o files. Is my assumption incorrect?
> I see that other modules are inconsistent in this area.
> If I'm right, other modules should be altered so that lib_SOURCES
> does not mention .h files; if I'm wrong, I'd like to know
> what lib_SOURCES is for, and perhaps other modules need to
> be altered so that their lib_SOURCES mention .h files.
I have re-trained myself to place in _SOURCES all kind of source like
files needed for building. I'm putting header files, linker scripts and
similar files there.
The automake manual have examples with .h files in _SOURCES:
The variable `hello_SOURCES' is used to specify which source files
get built into an executable:
hello_SOURCES = hello.c version.c getopt.c getopt1.c getopt.h system.h
/Simon
