Summary: | configure.in is deprecated in favor of configure.ac | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Steven T. Hatton <hattons> |
Component: | Build tools: Automake | Assignee: | 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
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" 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 Can fix this by removing the hard coded check for configure.in and checking for either configure.in or configure.ac. 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. |