Using Clang-Tidy in Visual Studio

Code Analysis natively supports Clang-Tidy for both MSBuild and CMake projects, whether using Clang or MSVC toolsets. Clang-Tidy checks can run as part of background code analysis. They appear as in-editor warnings (squiggles), and display in the Error List.

Clang-Tidy support is available starting in Visual Studio 2019 version 16.4. It's included automatically when you choose a C++ workload in the Visual Studio Installer.

Clang-Tidy is the default analysis tool when using the LLVM/clang-cl toolset, available in both MSBuild and CMake. You can configure it when using an MSVC toolset to run alongside, or to replace, the standard Code Analysis experience. If you use the clang-cl toolset, Microsoft Code Analysis is unavailable.

Clang-Tidy runs after successful compilation. You may need to resolve source code errors to get Clang-Tidy results.

MSBuild

You can configure Clang-Tidy to run as part of both Code Analysis and build under the Code Analysis > General page in the Project Properties window. Options to configure the tool can be found under the Clang-Tidy submenu.

For more information, see How to: Set Code Analysis Properties for C/C++ Projects.

CMake

In CMake projects, you can configure Clang-Tidy checks within CMakeSettings.json or CMakePresets.json.

Clang-Tidy recognizes the following keys:

• enableMicrosoftCodeAnalysis: Enables Microsoft Code Analysis
• enableClangTidyCodeAnalysis: Enables Clang-Tidy analysis
• clangTidyChecks: Clang-Tidy configuration. A comma-separated list of checks to enable or disable. A leading - disables the check. For example, cert-oop58-cpp, -cppcoreguidelines-no-malloc, google-runtime-int enables cert-oop58-cpp and google-runtime-int, but disables cppcoreguidelines-no-malloc. For a list of Clang-Tidy checks, see the Clang-Tidy documentation.

If neither of the "enable" options are specified, Visual Studio selects the analysis tool matching the Platform Toolset used.

CMake settings

To edit your Clang-Tidy settings, open your CMake settings, and select Edit JSON in the CMake Project Settings Editor. You can use the keys above to fill out your Clang-Tidy specifications in the CMake Settings JSON file.

An example CMake settings implementation looks like this:

{
  "configurations": [
  {
    "name": "x64-debug",
    "generator": "Ninja",
    ....
   "clangTidyChecks": "llvm-include-order, -modernize-use-override",
   "enableMicrosoftCodeAnalysis": true,
   "enableClangTidyCodeAnalysis": true
  }
  ]
}

CMake presets

The same keys can be used in your CMake presets via the vendor object.

An example CMake preset implementation looks like this:

"configurePreset": [
{ "name": "base",
  ....
  "vendor": {
    "microsoft.com/VisualStudioSettings/CMake/1.0": {
      "clangTidyChecks": "llvm-include-order, -modernize-use-override",
      "enableMicrosoftCodeAnalysis": true,
      "enableClangTidyCodeAnalysis": true
      }
    }
}
]

Warning display

Clang-Tidy runs result in warnings displayed in the Error List, and as in-editor squiggles underneath relevant sections of code. To sort and organize Clang-Tidy warnings, use the Category column in the Error List window. You can configure in-editor warnings by toggling the Disable Code Analysis Squiggles setting under Tools > Options.

Clang-Tidy configuration

By default, Clang-Tidy does not set any checks when enabled. To see the list of checks in the command-line version, run clang-tidy -list-checks in a developer command prompt. You can configure the checks that Clang-Tidy runs inside Visual Studio. In the project Property Pages dialog, open the Configuration Properties > Code Analysis > Clang-Tidy page. Enter checks to run in the Clang-Tidy Checks property. A good default set is clang-analyzer-*. This property value is provided to the --checks argument of the tool. Any further configuration can be included in custom .clang-tidy files. For more information, see the Clang-Tidy documentation on LLVM.org.

See also

Clang/LLVM support for MSBuild projects
Clang/LLVM support for CMake projects