Recommendations to others considering CMake:
If you're working in a small project (say less than 5,000 files), CMake is a good choice.
Regardless of what operating system you're developing on, and regardless of your targets, CMake is a good choice. It has a great community. If you have issues, there are plenty of people to help answer questions. If you are only on linux, mixing languages, and your codebase is very large, take a look at some of the build systems that have come out of Facebook / Google instead. Review collected by and hosted on G2.com.
What problems is CMake solving and how is that benefiting you?
Again, CMake solves the problem of cross-compilation through consistency of single build files.
Its pretty simple to take a working CMake example and roll with it. The barrier of entry to using CMake is low, but the difficulty increases as you attempt to do unique and novel things within your software build. Yet, I'd still say that CMake is much easier than writing raw Makefiles. CMake provides a hint of confidence to users in the open source community as well. I'm much more willing to contribute to a project if I see Cmake, as apposed to raw makefiles (or no build files at all). Review collected by and hosted on G2.com.