|
From: | Ralf Corsepius |
Subject: | Re: Motivation for renaming configure.in to configure.ac and its effect? |
Date: | Mon, 08 Mar 2010 12:29:02 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3 |
On 03/08/2010 12:12 PM, Steffen Dettmer wrote:
Hi, I'm trying to understand the motivation for renaming configure.in to configure.ac. If I remember correctly it was related to the fact that ./config.status or whoever else processes .in files.
The reason is suffix rules: *.ac's are processed by "autoconf" (written in the "autoconf-language") *.in's are arbitrarily formated, arbitrarily formated files. > Is the renaming configure.in to configure.ac cosmetic only No (cf. above) > and > is it safe to keep configure.in in old projects/branches?No, you should rename them. Keeping configure.in's doesn't make no sense at all.
Ralf
[Prev in Thread] | Current Thread | [Next in Thread] |