Re: [PATCH] autoconf: Use autoconf to write installation directories to config.mak

From: Jakub Narebski <jnareb@gmail.com>
Date: Jun 29, 2006, 13:48 UTC
Message-ID: <e80lnq$9mi$1@sea.gmane.org>
In-Reply-To: <E1FvvuX-0002Lr-Nt@moooo.ath.cx>

Matthias Lederhofer wrote:

Show 15 quoted lines

>> This is beginning of patch series introducing installation configuration
>> using autoconf (and no other autotools) to git. The idea is to generate
>> config.mak using ./configure (generated from configure.ac) from
>> config.mak.in, so one can use autoconf as an _alternative_ to ordinary
>> Makefile, and creating one's own config.mak.
> 
> Are you sure this should be named config.mak? From INSTALL:
>> You can place local settings in config.mak and the Makefile
>> will include them.  Note that config.mak is not distributed;
>> the name is reserved for local settings.
> 
> So with another filename either include it
> - before config.mak: the user may override ./configure options with
>   config.mak
> - after config.mak: ./configure overrides config.mak

The idea was to use ./configure to _generate_ config.mak, which the user can then edit.

But perhaps using another filename for results of ./configure script (and including it in main Makefile) would be better idea.

> At least do not overwrite config.mak if it exists.

But one might want to run ./configure with different options, to finally arrive at the set which is satisfactionary. So unless some magic to detect if config.mak was generated from ./configure script, or generated by user is used...

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git