Why I don't choose CMake, but Premake

Project Engineering management tools Cmake/premake have been used, and eventually abandoned the cmake for a simple reason:
1. Grammar from a set, not concise, there is no ready-to-use IDE support-_-!
2. And the biggest reason--not found it supports the method of generating a project file with relative path, SET (Cmake_use_relative_paths on) is a device, completely does not play any role, there is no need to force me to the project team every child shoes use the exact same check Out Path bar, otherwise it is necessary for each person to update the CMake file after the project file, after submission also need to rebuild the project ... This all the way down estimated that the sky is dark and bright ~

Finally determined to choose the implementation and grammar are more concise premake, after all, do the game more familiar with Lua (Blizzard also began to abandon CMake to use Premake)
The results also show that the choice is correct, early in the project Xcode/ndk/vs project one at a time (of course, later cross-platform for a variety of open Source Library modification is also many ~)

Finally, if any child shoes have to use cmake to generate relative path works also please advise ~

Why I don't choose CMake, but Premake