>> And do we really still need version 2.6 as default (we could bump this >> version to where current policies are still treated as warnings not >> errors)? > > To which default do you refer? Where in our code is it set? > Likely we cannot update it because it could change behavior > of existing scripts with no transition warning ever given.
I've read it in Mastering CMake and had to search for it today... On page 42 it says that by default if cmake_minimu_required is missing it sets policy version of 2.4. It's probably a technical back compatibility reason (cmake_minimum_required wasn't present back then?) and those scripts don't necessarily use any of the policies that will change but I was wondering if changing this to a newer version (2.6.8?) would be appropriate now that older policies will no longer support current OLD setting. Since the main reason I proposed that was fall back of CMake scripts that are missing cmake_minimu_required I guess that printing out a warning for scripts as well would also be fine. Regards, 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
