[Top][All Lists]

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

Re: rules, rules, and more (code policy) rules

From: Simon Josefsson
Subject: Re: rules, rules, and more (code policy) rules
Date: Thu, 16 Feb 2006 14:12:04 +0100
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

Simon Josefsson <address@hidden> writes:

> Jim Meyering <address@hidden> writes:
>> Simon Josefsson <address@hidden> wrote:
>>> Simon Josefsson <address@hidden> writes:
>>>>    * build-aux/Makefile.maint:
>>> I will hurt my fingers over this name (and the related Makefile.cfg),
>>> when completing for Makefile.am, so I would prefer to have names that
>>> doesn't begin with 'Makefile'.
>>> gnulib.mk and gnulib-cfg.mk?
>>> gnulib.mk and local.mk?  (Avoids auto-completion problem in previous)?
>>> maintainer.mk and local-maintainer.mk?
>> Ok.
>> How about maint.mk and maint-cfg.mk?
> Sounds good.  Installed.

Auto-completing maint* is causing me problem already...  while this is
very minor, it also occurred to me that "cfg" is rather incorrect.
maint-cfg.mk will likely contain a lot of local maintainer rules.

How about maint.mk and local.mk?

I've also discovered that maint-cfg.mk (or local.mk) is a very useful
place to put rules for various build environments.  E.g.:

W32ROOT ?= $(HOME)/w32root

mingw32: autoreconf 
        ./configure $(CFGFLAGS) --host=i586-mingw32msvc 
--build=`./config.guess` --prefix=$(W32ROOT)

Then I don't have to remember how to build it for mingw32 anymore.

reply via email to

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