Hi Simon, > Hi! Do we need to put link-warning.h in build-aux/? Since it is a C > header file, having it in the lib/ directory seems cleaner to me.
The file is not included by the C compiler. It's used by some Makefile rules that don't involve a compiler. Therefore build-aux/ is the natural place for it. http://lists.gnu.org/archive/html/bug-gnulib/2007-02/msg00189.html The suffix .h is only so that an editor can choose the right syntax highlighting automatically. > (I noticed this because my build-aux directory is '.', so all gnulib > scripts end up in my top-level project directory Ah, that's your problem with it! :-) I gave up this choice long ago. 'install-sh', 'missing', 'texinfo.tex', 'config.sub' etc. are not files that a user who looks into a package for the first time should see, IMO. Bruno
