On 02/10/2015 09:03 AM, Brad King wrote: > On 02/09/2015 05:14 PM, Domen Vrankar wrote: >> To get around this problem I thought about wrapping the entire script with: >> >> cmake_policy(PUSH) >> cmake_policy(VERSION 3.1) >> cmake_policy(POP) >> >> Would this be an acceptable solution? > > That is currently the intended way to do it.
I decided not to add a module-wide policy scope just before a release in case it causes other problems. Instead I converted the fix to set the policy locally: CPackRPM: Do not run file(GLOB_RECURSE) without CMP0009 set to NEW http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=be36bfd6 Please verify this still works for the original problem. Thanks, -Brad -- 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
