On Tuesday, April 29, 2014 16:38:56 Brad King wrote: > On 04/29/2014 04:25 PM, Alexander Neundorf wrote: > >> Or, you could fix your project to not use the behavior deprecated > >> by the policy. > > > > Other reasons are e.g. avoiding to annoy your developer team by warnings > > which don't matter (the build has been working, so there's no need to > > change it). > Yes, there is a need to change it. CMake deprecated an interface. > The project should stop using it and use the replacement interface > instead. The CMP0043 documentation explains how and gives examples.
I was talking in general about these warnings. Typically some project has a working build system (...otherwise it wouldn't build), and after updating cmake, warnings appear. Since the build is working, there is no immediate need (for the project) to change anything in the buildsystem. The project will have an urgent need to change it once the old behaviour is not supported anymore. Alex -- 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/cgi-bin/mailman/listinfo/cmake-developers
