Re: Autoconf 2.5x

Jerry James <james(a)xemacs.org&gt; wrote: It's been on my TODO list for a while. Unfortunately, I have no time for XEmacs right now, and I haven't done anything in that direction yet :-( The frightening complexity of our configure.in is mainly due to the fact that at the time it was written, many things we wanted to achieve were not available in autoconf. Many new features exist in autoconf 2.5 so things should indeed get simpler. Another reason for the size of our configure script is that many *standard* autoconf tests were also rewritten, sometimes, just to change one or two bits, like, increase the verbosity of the internal messages. I'm not sure if the purpose of rewritting such or such macro is well documented, and I'm afraid not. In that case, it will probably be tricky to figure out whether you can use the new 2.5* version, or whether you still need a rewritten version. In the worst case, you would end up comparing the code of our version with that of autoconf 2.13 and see what has changed. Also, if keeping a rewritten version is still needed, it's gonna be completely different fromn the current one because the internals of autoconf have changed a damn lot. Also, two good things to do in order the clean up the whole stuff, that just come to my mind: - use the aclocal mechanism to separate macro definition from their usage (that should have been the case with our current script already) - re-integrate the help file in the script (the 2.5* series have a better mechanism for handling cmd line options messages now) -- Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier(a)xemacs.org