> Why would you build targets you don't depend upon in my original proposal? > you certainly include them all in your project, but as long as you build your > application target, only it's actual dependencies will be built. Of course, > if you build the "all" target, everything will be built, but that could > easily be avoided with EXCLUDE_FROM_ALL when adding the `components` > subdirectory.š
Unfortunately, weāre using Visual Studio, which makes it very easy to āBuild Solutionā (which builds all targets, including the CMake-provided ALL_BUILD target), but more cumbersome to build just the application target. There is a default shortcut key for āBuild Solution,ā but to build just the application you have to use the UI menus :( Even if the EXCLUDE_FROM_ALL worked ā again, I believe Visual Studioās āBuild Solutionā just builds all Visual Studio projects that are part of the solution, regardless of what ALL_BUILD does ā having to track which libraries should be excluded from the ALL_BUILD target for each application boils down to manually tracking transitive dependencies š
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
