Mixing the build and source directory is really painful with CMake and is not how the system is supposed to be used. ), please check them out before proceeding. If you didn't do this so far (which I guess is the case, since you wrote cmake. The good news is that CMake does a good job of keeping a lot of this messiness away from you: Use out-of-source builds and you don't even have to look at the generated files. The secret is that you don't have to understand what the generated files do.ĬMake introduces a lot of complexity into the build system, most of which only pays off if you use it for building complex software projects. , what exactly is CMake configuring and generating before it builds the project? What is the purpose of these files, and when I type cmake. Not understanding what was going on behind the scenes (i.e: why so may files had to be generated and what their purpose was), was the biggest obstacle in being able to learn CMake. There are so many files generated: CMakeCache.txt cmake_install.cmake MakefileĪnd a CMakeFiles folder with so many files and folders: CMakeCCompiler.cmake CMakeOutput.log Makefile.cmakeĬmake.check_cache CMakeSystem.cmake progress.marksĬMakeCXXCompiler.cmake CMakeTmp TargetDirectories.txtĬMakeDetermineCompilerABI_C.bin CompilerIdC Tutorial.dirĬMakeDetermineCompilerABI_CXX.bin CompilerIdCXXĬMakeDirectoryInformation.cmake Makefile2 ![]() ![]() ![]() What exactly was going on behind the scenes when for such a small CMakeLists.txt file, cmake_minimum_required (VERSION 2.6)Īnd such a small tutorial.cpp int main()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |