#Cmake windows set warning level 4 code#

This external include directory will be added to the include search path as normal, but every header that in that directory or a subdirectory of it will be treated as external. You can find a new “External Include Directories” property for your projects under “VC++ Directories” which can be used to designate any include directory as containing external headers.

#Cmake windows set warning level 4 code#

This leaves you free to choose stricter settings for your project’s code to enforce code quality without getting bogged down with warnings from headers that are beyond your control. These external headers can have their own compiler warning level, code analysis, and template diagnostics settings. I’m happy to announce that, thanks to this feedback, external headers are now officially supported by the compiler, code analysis, and integrated into the IDE. Some of you may remember our previous post, Broken Warnings Theory, when we added experimental external header support to the Microsoft C++ Compiler. This is something we have been working on for a while with help and feedback from the community. To alleviate this, we’ve made it easy to mark headers as external to your project in the latest preview Visual Studio 2019. If you have tried to keep your code clean by selecting strict compiler warning levels or code analysis rulesets, you likely know how frustrating it can be to see these warnings for headers that are not part of your project.