3 ms·
Unfortunately even if you're starting a new project chances are that your dependencies are using cmake and they expect their dependencies to use cmake... in the
by aprdm 7y ago
Unfortunately even if you're starting a new project chances are that your dependencies are using cmake and they expect their dependencies to use cmake... in the end of the day you spend a lot of time fixing the upstream projects build files.
More than that CMake at this point is the ""standard"" and there are many others with a similar share of the market and selling points, it makes it harder to pick one that is not CMake.
- TonCherAmi 7y agoMeson supports CMake subprojects: https://mesonbuild.com/CMake-module.html#cmake-subprojects https://mesonbuild.com/CMake-module.html#cmake-subprojects
- Johnnynator 7y agoCMake subprojects was far from reliable last time I tested it. But this might also have been due to meson targeting unreleased CMake versions...
- stefan_ 7y agoIf your dependencies use CMake or not doesn't really matter, you still end up writing some FindX.cmake file. (Which is a whole other thing with this "modern CMake" by the way: only half of them that come with CMake are "upgraded" to modern and if you don't want to require the absolute latest version, you end up having to check what the FindX script did or redefine stuff manually)