Re: Removal of the autotools-based build system
Hartmut Holzgraefe <[email protected]>
| Newsgroups | gmane.comp.db.mysql.devel,gmane.comp.db.mysql.packagers |
|---|---|
| Message-ID | <[email protected]> |
Hi Alex, (replying to Davis reply as i don't seem to have received the original reply from Alex) On 11/09/2010 02:36 AM, Davi Arnaut wrote: > On 11/8/10 11:28 PM, Alex Esterkin wrote: >> No, configure.ac and configure.in are NOT the same thing. If you do not >> know the difference, I am not surprised your team had difficulties > > The autoconf manual is wrong? same thing for me (and Davi knows that i'm quite a bit biased to the autotools side ;) configure.in was simply renamed into configure.ac as the .in extension was confusing, implying that configure.in would be used as template in the configure step. Hence the decision to rename it to clearly mark it as an input file to autoconf, not configure >> maintaining the automake based build system. what's automake got to do with configure.(in|ac)? autoconf processes it, not automake (or autoreconf if you take autotools as a bundle) >> A properly written >> configure.ac file is orders of magnitude smaller in size than a >> comparable >> configure.in. > > What is the difference between configure.ac and configure.in files? i sense some confusion about Makefile.am -> Makefile.in (where "orders of magnitude smaller" is true for sure) and configure.ac/configure.in here ... there is no such thing as a configure.ac -> configure.in expansion step though -- hartmut -- MySQL Internals Mailing List For list archives: http://lists.mysql.com/internals To unsubscribe: http://lists.mysql.com/[email protected]