On 05/15/2014 04:02 PM, Brad King wrote:
On 05/15/2014 09:50 AM, Nils Gladitz wrote:
Yes, that makes sense. The keys could each be either a relative path
(to the install prefix) or an absolute path. We would not need any
new commands. The set_property and get_property command could learn
a new type for this. Do you have a name in mind?
Assuming there are no use cases which would make these properties useful
at install time as well I would suggest "CPACK" otherwise "INSTALL".
A single (optional)
- cmake_package.cmake
- cpack_properties.cmake
- or CMakeCPackProperties.cmake?
file in the root directory might also make more sense when CPack is used
without CMake.
The reason cmake_install.cmake is sprinkled in each directory is so
the makefile generators can support "cd subdir; make install".
I do not think we support this with CPack so a single file at the
top makes sense. I think the name should start in "CPack" but
otherwise have no preference currently.
Then perhaps "CPackProperties.cmake" in case this stays CPack specific
and "cmake_install_properties.cmake" otherwise.
Nils
--
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/cgi-bin/mailman/listinfo/cmake-developers
