Hello, We have a set of configuration files located in a common location that multiple target rely on at runtime.
The structure looks something like this; root - CMakeLists.txt - targetA - CMakeLists.txt - targetB - CMakeLists.txt - targetC - CMakeLists.txt - common - config.xml - config.ini Both targetA and targetB depend on config.xml and config.ini. TargetC does not depend on the files. What is the preferred way using CMake to install the resource given the above mentioned dependencies? Two options; - add CMakeLists.txt to common folder and install files from there. Do not like this option as this means I always install the files regardless of which target I want to install (targetC does not require does files). - add install rules to targetA/CMakeLists.txt and targetB/CMakeLists.txt. This is a better option but still requires same logic in multiple files. Any other options? Regards, Lars
-- 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://public.kitware.com/mailman/listinfo/cmake
