4 ms·
OT I know, I cant help but feel a little smug when I see cool projects like this and they use cmake, and not autotools. Thank you cmake, you've made working in
by shadowmint 13y ago
OT I know, I cant help but feel a little smug when I see cool projects like this and they use cmake, and not autotools.
Thank you cmake, you've made working in the C ecosystem fun again.
- greggman 13y agoCheck out gyp and ninja https://code.google.com/p/gyp/wiki/GypVsCMake https://code.google.com/p/gyp/wiki/GypVsCMake https://github.com/martine/ninja https://github.com/martine/ninja
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- randallu 13y agoCMake is pretty horrifically inefficient at compiling WebKit. The makefiles it generates fork to call CMake (to do things like printf in color) far more than they fork to call the compiler. The ninja generator is better, but it has various issues with long command lines on WebKit currently (trunk CMake fixes some of these, but then it doesn't make some directories in the output directory). Also, the CMakeLists syntax is pretty nasty IMO, but it feels like gyp, cmake and autotools are in some kind of syntax ugliness competition... (Maybe because nobody ever wants to work on a build system, so they'll just do this one little hack which inevitably grows tentacles).