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. There was once some discussion of trying to scope policies automatically for modules within CMake, but currently it must be explicit. -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
