H
Hans Loeblich
Guest
I have a project that is building the main application using VS2017 Community Edition cmake integration. I have CMakeLists.txt and CMakeSettings.json in the main directory and they are working fine currently.
I also have a tests\CMakeLists.txt file to build the tests that I would like to run completely separately. I would prefer not to use add_subdirectory in my main CMakeLists.txt because one of the first things that tests\CMakeLists.txt does is look for the already built executable, and I don't want to change behavior significantly for existing platforms/build scripts which are not running MSVC.
Is there any way to incorporate this "separate" cmake project? Would the tests directory need its own CMakeSettings.json? Or can I do something like specify different configurations/targets to use the tests\CMakeList.txt from the main CMakeSettings.json?
Continue reading...
I also have a tests\CMakeLists.txt file to build the tests that I would like to run completely separately. I would prefer not to use add_subdirectory in my main CMakeLists.txt because one of the first things that tests\CMakeLists.txt does is look for the already built executable, and I don't want to change behavior significantly for existing platforms/build scripts which are not running MSVC.
Is there any way to incorporate this "separate" cmake project? Would the tests directory need its own CMakeSettings.json? Or can I do something like specify different configurations/targets to use the tests\CMakeList.txt from the main CMakeSettings.json?
Continue reading...