Bug 111686

Summary: configure.in is deprecated in favor of configure.ac
Product: [Applications] kdevelop Reporter: Steven T. Hatton <hattons>
Component: Build tools: AutomakeAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: normal CC: pocm
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Steven T. Hatton 2005-08-29 05:03:32 UTC
Version:           3.2.90 (using KDE 3.4.2 Level "b" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.8-default

This is from autoconf.info,  Node: Writing configure.ac

" Previous versions of Autoconf promoted the name `configure.in', which is somewhat ambiguous (the tool needed to process this file is not described by its extension), and introduces a slight confusion with `config.h.in' and so on (for which `.in' means "to be processed by `configure'").  Using `configure.ac' is now preferred."

I know it's a minor issue, but it's a good thing to try and conform to recommendations when possible.  I've noticed KDevelop generates a configure.in rather than a configure.ac.
Comment 1 Matt Rogers 2005-08-29 14:07:31 UTC
kdevelop is still supposed to work with older versions of autoconf. Find out what version configure.in was deprecated in, and then we can look at reopening this "bug"
Comment 2 Paulo J. Matos 2006-11-01 20:59:18 UTC
This bug should be reopened and solved. After chatting on #kdevelop:
Checking ChangeLog.2 of current autoconf sources:
In 1999, version 2.13 of autoconf was out, 2.14a also got out but in the meantime (in May, 2000) autoconf developers said configure.ac should be promoted over configure.in. 2.49[a|b|c] came out soon after and 2.50 was released in 2001. Since then configure.ac is standard and the one which should be used. What I can't understand is how kdevelop still uses configure.in. Do you truly believe anyone still uses <=2.14?

Regards,

Paulo Matos
Comment 3 Megan Webb 2006-11-02 10:08:58 UTC
Can fix this by removing the hard coded check for configure.in and checking for either configure.in or configure.ac.
Comment 4 Megan Webb 2006-11-02 10:16:11 UTC
r601133 | webb | 2006-11-02 19:47:16 +1100 (Thu, 02 Nov 2006) | 9 lines

BUG: 111686
BUG: 67746

Importing project - version is read from configure.[in.in|in|ac]. Check for configure.[in|in.in|ac] when trying to create automake project, and don't fail i
f there is no AUTHOR file.
Changing the version in project options - updates configure.[in.in|in|ac] if they exist. Added tool tip advising that automake may need to be run to update
all files.
Removed hard coded references to configure.in - if imported project uses configure.ac, then this will be updated.
Tooltip in import dialog telling format of author/email fields.