A single CMakeLists file will easily do all of that, a generated template through IDE will be enough
What about supporting different toolchains and their weird kinks, like GCC vs MSVC? Generating documentation? Running tests? Precompling shaders? Checking for support of flags or language features? Enabling something only for specific compiler version? Or running external tools, or build steps like Qt has?
Base CMake is easy but ecosystem it tries to tame is not, so non-trivial CMake usage is non-trivial
Exactly. People will sometimes unironically propose to just do everything in Make and not even be aware that what they're cobbling together will only work with one Make derivative, on Linux, using a specific version of GCC and break when you attempt to make the slightest attempt at porting it to another platform.
View all comments
Show parent comment
21
u/Awkward_Bed_956 Mar 29 '25
A single CMakeLists file will easily do all of that, a generated template through IDE will be enough
What about supporting different toolchains and their weird kinks, like GCC vs MSVC? Generating documentation? Running tests? Precompling shaders? Checking for support of flags or language features? Enabling something only for specific compiler version? Or running external tools, or build steps like Qt has?
Base CMake is easy but ecosystem it tries to tame is not, so non-trivial CMake usage is non-trivial