On Friday 26 May 2006 21:42, Brandon J. Van Every wrote: > Another issue is that an autoconf ./configure script typically relies > on libtool. You don't wanna go there.
Read my other mails in this thread please; its the NAME ONLY I suggested to use. If the configure script is just 4kb and does nothing but provide a familiar front end to the cmake command (which I asserted earlier is not user friendly enough) then I'm happy. Nobody was suggesting to go back to auto* > As for functionality: the point of an autoconf ./configure is that you > don't need any special tool installed to run it. Actually; the point of configure is to provide a usable way to alter settings, especially in a project you have never compiled before. Otherwise we could all go back to editing config or even Makefiles. Any idea how much time was gained in total (over the last years) by not having users come and ask how to install it in /opt instead of the default /usr/local ? :-) -- Thomas Zander
pgpnjlJGoXzey.pgp
Description: PGP signature
_______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
