3 ms·
I think the primary use case is building the same code on multiple platforms. A developer can write a single CMakeFile and then CMake will generate Makefiles/Ni
by juanbyrge 5y ago
I think the primary use case is building the same code on multiple platforms. A developer can write a single CMakeFile and then CMake will generate Makefiles/Ninja files/VS soln files/etc depending on the underlying platform.
- MiddleMan5 5y agoI've used CMake for a number of larger projects. When you start having to deal with external dependencies or cross platform support it definitely fills in some of the holes in the C-style build ecosystems One of the things I've never been a fan of is that for whatever reason, the build steps that you see in basically every project are: - mkdir ./build - cd ./build - cmake configure ../ - make build Has no one thought of simplifying that??
- pjmlp 5y agoYes, we write a shell script and move on.
- jcelerier 5y agohttps://github.com/jcelerier/cninja https://github.com/jcelerier/cninja
- AHTERIX5000 5y agoYou can simplify it to cmake -B build && make -C build for example