Hi all. We have a setup where subprojects register "items" they wish to install, and the top-project later processes them (removing some, modifying others etc.) and issues install(...) commands for them. Currently, this does not work for install(TARGETS ...), as that command can only be given in the CMakeList which defined the target.
I'm curious about the reason for this limitation - why can't a target's installation be controlled by a different CMakeLists.txt file? Could anyone shed some light on this? Thanks. Petr
-- 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: http://www.cmake.org/mailman/listinfo/cmake
