Disabling external header code analysis when using integrate install with VS2022?

[micka190]

I'm using Visual Studio 2022 with vcpkg. I've run the vcpkg integrate install command to use libraries inside VS2022 without using CMake (nothing against CMake, but some of the packages I'm using have less than stellar support for it, and I'd rather they "just work" for these side projects).

I'm running into an issue with code analysis where it gives me hundreds of warnings from external library headers.
For example, the libnoise package has 269 warnings.

I've followed the steps in this C++ Team Blog post to disable code analysis in external headers, but it seems that vcpkg headers aren't recognized as external headers, because it isn't working. I've also tried adding them manually to my "External Include Directory" options under my project's Properties, but that hasn't done it either.

I'm guessing vcpkg appends its include directories at the end of the regular include directories list?

Is there any way to disable code analysis for external headers added by vcpkg when using integrate install? Or do I have to use CMake and configure it manually through that?

---

Here are some screenshots.

Here's what my External Include Directories look like:

Here are my External Includes settings:

But I still get warnings:

[DownerCase]

Raising this one from the dead a bit but I've run up against the same problem in a different situation. I tried turning on enableMicrosoftCodeAnalysis in my CMakePreset Vendor map, set a ruleset and enabled disableExternalAnalysis to prevent excessive warnings from code that isn't mine. I was very disappointed to then get flooded with warnings when running the analysis...

Interestingly Ninja correctly marks the vcpkg include as external and disables warnings.
INCLUDES = <snip> -external:IF:\dev\<snip>\vcpkg_installed\x64-windows\include -external:W0

However, when running the code analysis it executes:

cl " "/DWIN32" "/D_WINDOWS" \
"/GR" "/EHsc" "/Ob0" "/Od" "/RTC1" "-MDd" \
"/IF:\dev<snip>\vcpkg_installed\x64-windows\include" \
"F:\dev\<snip>\src\test.cpp" \
"/analyze:projectdirectoryF:\dev\<snip>" "/external:W0" "/external:env:CAExternalPath" "/analyze:external-" \
"/analyze:rulesetdirectoryC:\Program Files\Microsoft Visual Studio\2022\CommunityRelease\Team Tools\Static Analysis Tools\Rule Sets" \
"/analyze:rulesetC:\Program Files\Microsoft Visual Studio\2022\CommunityRelease\Team Tools\Static Analysis Tools\Rule Sets\NativeRecommendedRules.ruleset" \
"/c" "/Zs" "/errorReport:none" "/analyze" "/analyze:logF:\dev\<snip>\CodeAnalysis\results.sarif" "/DCODE_ANALYSIS" \
"/analyze:pluginC:\Program Files\Microsoft Visual Studio\2022\CommunityRelease\VC\Tools\MSVC\14.36.32532\bin\HostX64\x64\EspXEngine.dll"

My CMake Preset vendor map:

"microsoft.com/VisualStudioSettings/CMake/1.0": {
          "enableMicrosoftCodeAnalysis": true,
          "codeAnalysisRuleset": "NativeRecommendedRules.ruleset",
          "disableExternalAnalysis": true
}

Using Visual Studio 17.6.5 and latest vcpkg

[crud89]

Just experienced the same issue using latest vcpkg and VS 17.11.5. It appears to only affect certain headers, so maybe this is related to individual ports, but I am not sure. Did you find any solution to this?

[DownerCase]

No, I gave up and relied on clang-tidy instead.

Wasn't even sure which tool was at fault vcpkg, CMake, or VS.
Would be nice to have it work though. A minimal repro with the latest tools would, as always, be a good start for sure.