Re: [CMake] Forcing a target to be built if another target is built

That is roughly what I am saying. In my head you had a layout that looked like -> root_dir --> module_A --> tests_A --> module_B --> tests_B So while it is tedious to have module_A explicitly add tests_A it would be a possible solution. The problem is one of graph building. Currently the CMake

Re: [CMake] Forcing a target to be built if another target is built

I'm not sure I completely understand what you mean but I think your suggestion would be to list *all* needed subdirectories in the active project. This is not what a want. The active project simply lists its *direct* dependencies (via target_link_libraries) and CMake then figures out all the

Re: [CMake] Forcing a target to be built if another target is built

Have you thought about not doing anything in the root CMakeLists for your testing directories but instead inside the active project you use add_subdirectory ( it supports relative paths to handle directories not physically nested inside it ). On Wed, May 9, 2018 at 8:56 AM Job Noorman