Hi Brad,
The hunk I included at the bottom of the message
Ah yeah, sorry missed that part in the message, I understand the change
that needs to be done now.
The current caching logic still needs some work
One idea that comes to mind, is to change it so that it doesn't enable
dev/deprecated warnings by default by setting the DiagLevels map,
instead we create a specific function to get the status of dev warnings
suppression, which checks the cache variables (now set only if user
explicitly used -W options) but by default returns a value to signify
enable dev warnings. I think this would get around the mentioned issue,
but needs some playing about with to see if its a solution.
Cheers,
Michael
--
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
