The end result was a love/hate relationship with cmake.
Clearly, the weakness is its hokey scripting language. The shame is that if they'd just started with something halfway reasonable like lua it would have been easier to build the tool and it would be far more powerful. Instead, they couldn't resist writing their own DSL where everything you need to do is possible but just barely. I've done so many zany hacks over the years to force it to do what I needed.
Granted, I did the major porting work to cmake 2.4. The newer versions are certainly better (no more duplicating the expression in IF()/ELSE()/ENDIF() statements!) but it's still pretty painful to write something non-trivial compared to any modern scripting language.
However, the results of cmake are fantastic. Once you've got your CMakeLists.txt's working you can largely forget about it -- it'll just work, completely cross platform. If you need to target both UNIX compilers and the Visual Studio world it's probably the best solution.
A. It's what everyone else is using.
B. It's simple to do common things.
C. It's pretty darn fast with the Ninja backend.
The only downside seems to be that the cmake language is ugly and limited. Fortunately, I only need to write a tiny amount of cmake code to build most of my projects, since find_package is so good. (Though, it probably sucks to be the guys making that work.)
To be honest, every tool I've tried has kind of sucked. cmake just sucks the least. One day I'd like to investigate tup and shake, though.
cmake has won.
The other build tools tried (scons, premake, autotools) and they failed.
You don't like the syntax? Cry me a river.
It does the job. None of the other ones do.
Pragmatism > idealism. I don't care how pretty your build files are, if they don't actually work.
/shrug.
The best feature of CMake for me has been easy cross compiling so I can develop and remote debug Windows apps on my Linux box.
Stay away from cmake.