![]() It's not technically wrong it just describes HOW it works, but not WHAT it does. The statement about CMake being a "build generator" is a common misconception. Even if you're GNU-Make-only now, what if you later decide to expand to other platforms (be it Windows or something embedded), or just want to use an IDE? Using a buildsystem generator makes your project more future-proof. CMake itself also provides some nice features like dependency detection, library interface management, or integration with CTest, CDash and CPack. I would always recommend using CMake (or another buildsystem generator, but CMake is my personal preference) if you intend your project to be multi-platform or widely usable. If you have Windows developers used to Visual Studio and Unix developers who swear by GNU Make, CMake is (one of) the way(s) to go. So if you have a platform-independent project, CMake is a way to make it buildsystem-independent as well. From the same starting point, the same CMakeLists.txt file. ![]() It can produce Makefiles, it can produce Ninja build files, it can produce KDEvelop or Xcode projects, it can produce Visual Studio solutions. Make (or rather a Makefile) is a buildsystem - it drives the compiler and other build tools to build your code.ĬMake is a generator of buildsystems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |