Paul Floyd wrote: > Torsten Paul Eichst?dt wrote: >> References: >> 1. http://de.wikipedia.org/wiki/Autoconf >> german, but the english version doesnt include critcs; maybe some native >> english speaker >> can add some?) >> In short: There's a section called critics, stating auto* works well on >> Linux/GNU (add from >> me: or, with some luck, any modern UNIX as long you use gcc + a bunch of >> GNU tools you >> otherwise probably dont need), but often fails on other systems. It has >> several >> weaknesses. (I didnt write that article) >> 2. http://lwn.net/Articles/188693/ "Why the KDE project switched to CMake >> -- and how" >> >> We need autotools for the deps and KBE, right? > > IMO autocrap has a very high smeg factor. It's well suited to Linux, > where you never know if you're coming or going (borked libs, borked > compilers, borked headers, borked interpreters). > > It beats me why KDE doesn't use qmake. Surely to build KDE, you must > have qmake available?
KDE3 uses the auto*tools/libtool for building, KDE4 uses cmake. So, at least insofar as KDE4 is concerned, your wish has been granted: you no longer have to use auto*stuff/libtool to build KDE4. However, this is the KDE Solaris Project. It is beyond the scope of this Project to entertain any Grandiose Plans(TM) of "Rewriting All the auto*tools/libtool Build Systems To Use Something Else Which Would Make Everyone Happy". --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman at Sun.COM
