Our working relationship aside, CMake has greatly improved the process of building KDE. Projects using CMake take less time to get started, since there is less time spent fighting with the build system. One KDE developer says, "CMake doesn't make you want to shoot yourself with a nailgun when building your project anymore."

http://dot.kde.org/2007/02/21/road-kde-4-cmake-new-build-system-kde http://lwn.net/Articles/188693/

Maintaining multiple build inputs is a royal pain. And at least one of them is always out of step. Keeping Visual Studio projects and autotools-based Makefile.am files updated is very error-prone. Even the subset of developers that have ready access to both can get it wrong...We looked at a number of alternatives and settled on CMake.

http://stevehuston.wordpress.com/2009/05/14/why-apache-qpids-c-build-is-switching-to-cmake/

http://stevehuston.wordpress.com/2009/06/01/how-we-converted-the-apache-qpid-c-build-to-cmake/

"A great technology choice that our community helped us make was moving to CMake, a cross-platform build tool, which makes it much simpler to maintain makefiles for many different platforms."

http://wiki.secondlife.com/wiki/CMake

These These tools provide us with the ability to manage a development environment that is cross-platform, supports code reuse, and is responsive to change.

Andrew MacClean Article

Good integration with the popular IDEs (Visual Studio, Xcode, Eclipse CDT, KDevelop). Developing in an IDE makes the development process more enjoyable, and potentially it lowers the barrier for external contributors. Of course, CMake can generate traditional Unix Makefiles, which appear to be are superior to the ones generated by GNU autotools (for example, they have progress indicators, colored output and working dependencies).

http://www.lenzg.net/archives/291-Building-MySQL-Server-with-CMake-on-LinuxUnix.html

The first CMakeLists.txt file entered one of our repositories in April 2006 with the commit message "CMake, for easier Windows distribution" (this was clearly the perspective of a Linux developer tired of dealing with Windows). After some experimentation, doubts, and dabbling with alternatives, it became clear that CMake was a huge win. It gave a first-class experience to MSVC users when compiling projects developed by Linux users, and vice versa. Most of the time, developers could now forget about any development environment other than their own, and our community became a lot less "balkanized".

http://eris.liralab.it/wiki/CMake_Usage

http://www.kitware.com/products/archive/kitware_quarterly0410.pdf

"ASPEED's SDK supports a wide range of platforms and languages, and CMake fit the bill perfectly for our build and release cycle. It works for Visual Studio IDE development, and it works from the command line under either Windows (nmake) or Linux. It works for FORTRAN as well as C++. It's an enormous time-saver, allowing us to quickly develop applications for multiple platforms. This in turn has allowed us to build, test and release software more frequently, giving us a market advantage." (Mike Dalessio, Head of Development, ASPEED Software)

"I started to develop on a project on Linux OS in C++ language on 3 January 2005, and I had never written from scratch any configure.in files, nor used autoconf tools seriously before. So since one of my task was to create the building process for the whole project, I had 2 choices: learn and use autoconf, or search in Internet for an alternative. The one day research ended up in CMake.org, which is an easy but very powerful tool, which allowed me to achieve all I wanted to do (debug/release/profile compilations, compilation based on the developer name, easily maintainable and customizable compilation of many shared/static libraries and applications), and which has a very fast learning curve, exactly what a projet need to achieve its aim in short time." (Luca Cappa)

http://www.eetimes.com/showArticle.jhtml?articleID=197002559