Besides weird and clumsy syntax CMake has one great advantage over herds
of others so-called "build systems" (waf, scons, gyp ... <put your name
here>) - cross compilation, and being a packager, you should be aware of
that. CMake has indeed decent support of it. And this point gives CMake
100 points ahead of others "build systems".
On 03.07.2014 11:40, Aleksej Saushev wrote:
As a packager I can tell you that CMake goes the next in line after
SCons, certainly much higher than autoconf, which makes it rather bad
choice for portable software. In this respect (as in many others) I
don't see how it is any improvement over Make. It is an improvement
only in one sense: it has only one dialect. Once you realize it, you
understand that you could have insisted on using one particular Make
dialect which is exactly what Chicken does. Besides, generating
CMakeLists automatically makes it really suspicious.
I'm currently experimenting with automatic dependency extraction.
Unfortunately, apart from make with gcc -M combination, toolchains do
not expect dependencies jumping into the build graph when the process
already started. Also this breaks parallel compilation. I have some
ideas but not yet figured out how to handle this cleanly.
_______________________________________________
Chicken-hackers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
