![]() ![]() ![]() To add this folder to your CMake path: set(CMAKE_MODULE_PATH "$/CMakeLists.txt" LOC_PATH) An set of some common helpers is at /CLIUtils/cmake. You often want a cmake folder, with all of your helper modules. ![]() Use add_subdirectory to add a subdirectory containing a CMakeLists.txt. That's also why there is a directory for your project inside the include directory. This is because you should be able to copy the contents of the include directory to /usr/include or similar directly (except for configuration headers, which I go over in another chapter), and not have any extra files or cause any conflicts. Notice a few things already apparent the CMakeLists.txt files are split up over all source directories, and are not in the include directories. You'll also sometime see a python folder for python bindings, or a cmake folder for helper CMake files, like Find.cmake files. tests/, and the application folder may be called something else (or not exist for a library-only project). The names are not absolute you'll see contention about test/ vs. Keep from muddling and complicating your build.įirst, this is what your files should look like when you start if your project is creatively called project, with a library called lib, and a executable called app: - project.Easily read other projects following the same patterns,.This is based on convention, but will help you: I'm going to tell you how to structure the directories in your project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |