Why the KDE project switched to CMake -- and how
Posted Jun 23, 2006 10:00 UTC (Fri) by neiljerram
Parent article: Why the KDE project switched to CMake -- and how
As far as I can tell from the CMake web pages, CMake doesn't appear to cover two big areas that are covered by autoconf/automake/libtool, namely:
(1) checking for availability of particular headers, functions, libraries, or OS-dependent behaviour of existing functions (and adjusting defines and flags accordingly)
(2) knowing how to build and link shared libraries correctly on all the Unix-like OSs.
In other words, CMake is an alternative automake (whose notable extra feature is that it can generate MSVC project files as well as Unix makefiles), not an alternative autoconf/automake/libtool.
Is that correct, or have I misunderstood?
to post comments)