> My motivation is this. I want to submit a few improvements to the way CPack > writes config files, starting with that cpack_set_if_not_set change I > mentioned a while back. This functionality is generator-independent (and > basically unrelated to actual package generation), so I thought > RunCMake.CPack was not the appropriate place to test it.
Yes you're right, RunCMake.CPack is meant for specific generators and adding target 'none' or something similar would just make a mess. > Since there doesn't seem to be a test suite specifically for config file > writing, I thought I'd create one in a separate patch so that my later > patches don't have as much boilerplate in them. The Simple test is just > there to ensure I don't break the simple case while changing the more > complex ones. Well, and it would be silly to submit a test suite with no > tests in it. I've added your test: http://www.cmake.org/gitweb?p=cmake.git;a=commit;h=674dc0b Thanks, Domen -- 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-developers
