From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Narebski Subject: Re: [PATCH] autoconf: Use autoconf to write installation directories to config.mak Date: Thu, 29 Jun 2006 15:48:48 +0200 Organization: At home Message-ID: References: <200606290301.51657.jnareb@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-From: git-owner@vger.kernel.org Thu Jun 29 15:50:10 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FvwuH-0005Y4-KV for gcvg-git@gmane.org; Thu, 29 Jun 2006 15:50:09 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750722AbWF2Ntc (ORCPT ); Thu, 29 Jun 2006 09:49:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750737AbWF2Ntc (ORCPT ); Thu, 29 Jun 2006 09:49:32 -0400 Received: from main.gmane.org ([80.91.229.2]:64406 "EHLO ciao.gmane.org") by vger.kernel.org with ESMTP id S1750722AbWF2Ntb (ORCPT ); Thu, 29 Jun 2006 09:49:31 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FvwtU-0005KV-0Z for git@vger.kernel.org; Thu, 29 Jun 2006 15:49:20 +0200 Received: from host-81-190-27-124.torun.mm.pl ([81.190.27.124]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Jun 2006 15:49:20 +0200 Received: from jnareb by host-81-190-27-124.torun.mm.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Jun 2006 15:49:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: git@vger.kernel.org X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: host-81-190-27-124.torun.mm.pl Mail-Copies-To: jnareb@gmail.com User-Agent: KNode/0.10.2 Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Matthias Lederhofer wrote: >> 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