On 03/28/2016 01:49 AM, Geoffrey Viola wrote: > Thanks for the feedback. I’ll have to look more in-depth at Xcode specific > issues. >> Take a look at this approach: >> * https://github.com/ruslo/sugar/wiki/Cross-platform-warning-suppression > > I took a look at your repository. It’s very sophisticated.
I'd prefer to see an approach that abstracts the warning levels in a similar way to COMPILE_FEATURES, COMPILE_DEFINITIONS, INCLUDE_DIRECTORIES, etc. Project code would set directory or target properties to specify warning levels and the generators would map them to the proper flags or project file settings automatically. Something like this has long been missing for compiler warnings and optimization levels. -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
