[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: link-warning a build-aux file?

From: Simon Josefsson
Subject: Re: link-warning a build-aux file?
Date: Tue, 27 Feb 2007 07:45:57 +0100
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.94 (gnu/linux)

Bruno Haible <address@hidden> writes:

> 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.

I tried that now, since I kind of agree with the reasoning, although
this breaks the maintainer-makefile module that I'm using in several
projects.  The module contains a 'GNUmakefile' that really need to be
in the top-level directory to make sense.  Any ideas how to resolve


reply via email to

[Prev in Thread] Current Thread [Next in Thread]