Why the KDE project switched to CMake -- and how (continued)

Posted Jun 22, 2006 12:36 UTC (Thu) by akumria (guest, #7773)
In reply to: Why the KDE project switched to CMake -- and how (continued) by aleXXX
Parent article: Why the KDE project switched to CMake -- and how (continued)

> Today KDE 4 builds with cmake on more platforms than KDE 3 with autotools
> ever did, with full configure checking on all platforms and all
> compilers/IDEs.

autotools = automake + libtool + autoconf

What both the two previous posters were pointing out is that if you project is just using autoconf there may not be the same benefit in switching to cmake.

to post comments

Why the KDE project switched to CMake -- and how (continued)

Posted Jun 22, 2006 14:11 UTC (Thu) by aleXXX (subscriber, #2742) [Link] (2 responses)

I'm not sure there are many projects using autoconf together with
handwritten makefiles without automake and libtool.
CMake has compared to autoconf alone e.g. the advantage that it also
supports MSVC under Windows and that it can not only generate Makefiles,
but also project files (Xcode, MSVC, KDevelop3), which you cannot achieve
with handwritten makefiles.

Alex

Why the KDE project switched to CMake -- and how (continued)

Posted Jun 23, 2006 3:54 UTC (Fri) by jamesh (guest, #1159) [Link] (1 responses)

Some prominent ones that come to mind are Mozilla and Python. There are others, but autoconf is definitely used in more projects than automake (which is no surprise since automake requires autoconf but not vice versa).

Why the KDE project switched to CMake -- and how (continued)

Posted Jun 23, 2006 20:13 UTC (Fri) by nix (subscriber, #2304) [Link]

Mozilla, Python, GCC, Emacs, XEmacs... the list is long.

A brief scan of the packages I have unpacked here reveals 1319 using Autoconf, of which 835 use Automake.