CMake will mirror your add_subdirectory() and CMakeLists.txt directory structure in its generated build environment.To achieve this your project structure may have to adapt, if "each source file from the subfolders creates a separate executable".Īnd the root CMakeLists.txt is your starting point and contains the project() command. The most commonly used rule is "One CMakeLists.txt per target". (I'm a cmake noob, trying to convert a relatively large project to use cmake)
Looking at projects using cmake I see no consistency, so this doesn't help much. All the tutorials I could find for multi-directory project deal with the case when there's a standalone library in one folder, standalone application using that library in another folder and standalone tests using the same library in yet another directory. I would like know which is the "preferred" way in a "modern" cmake project. The third option seems like an easy way to quickly create a CMakeLists.txt file with a length of a spaghetti, so it possible I would prefer something else. I would also have to prefix the names of output files. If there's only one level of nesting (like for first two example subfolders) it is ok, but for some/deeply/nested/path/SomeFeature-unit-test this is not so nice.
Cmake vs make file difference full#
But then in each some-random-name.cmake in subfolders I have to use full path to source files, which is against my desire for each of them to be self contained. The second option seems to clearly suggest that there is only one cmake project here. The first option is the most convenient, but it suggests that each subfolder is actually a standalone project which could be compiled separately.
0 kommentar(er)
