On 17.09.2014 14:48, Nils Gladitz wrote:
Maybe modules loaded from the cmake installation itself should implicitly have their policy version set to the current cmake version?
I pushed "root-modules-set-policies-new" to stage which sets all policies to NEW for modules from cmake's own Modules directory if NO_POLICY_SCOPE is not used.
I haven't merged it to next yet in case someone things this is the wrong thing to do in general.
I figured since the new behavior only applies to cmake's own modules it should not require a policy.
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/mailman/listinfo/cmake-developers
