Sonarlint VS 2022 with CMake Presets

[JuliusCaesar89 (Julian)]

Please provide

• Operating system: Win 10
• SonarLint plugin version: newest (7.2.0)
• Programming language you’re coding in: C/C++
• Is connected mode used:
  • Connected to SonarCloud or SonarQube (and which version): no

And a thorough description of the problem / question:
Hey guys,
Some time ago I posted a question how to get sonarlint to work with VS2022 and CMake Presets.
The answer was to use a CMakeSettings and export as Compile Commands

Sonarlint Configure Project Type in VS2022

Hey Ugras, thank you for your answer I added the buildRoot in the AppData/Romaing/…/settings.json { "sonarlint.rules": {}, "buildRoot": "C:\\git\\xxx\\build\\windows_ninja_debug" } but this did not work. Is there a way to set this property per project and not globally like in the AppData/Romaing folder?

However in the mean time, Microsoft managed to break Ninja generator. When using VS we can only configure our project using the VS2022 Cmake Generator not ninja any more.

Unfortunately CMAKE_EXPORT_COMPILE_COMMANDS does only work for Ninja Generator, not for the VS generator. Therefore the suggested solution does not work for me any more.

=>How far has the CMakePresets integration gone? Are CMake Presets now supported directly?
=>Is there any other way to get sonarlint running.
(Obviously i could open the generated .sln file and sonarlint would work, however I’d like to switch between different configurations, which is the main benefit of using cmake presets)

thx for your help guys
greets Julian

[mpaladin (Massimo Paladin)]

Hi @JuliusCaesar89 ,

@JuliusCaesar89

=>How far has the CMakePresets integration gone? Are CMake Presets now supported directly?
=>Is there any other way to get sonarlint running.

We do not support CMakePresets, we clearly state it in the documentation page: Requirements - Visual Studio.

@JuliusCaesar89

However in the mean time, Microsoft managed to break Ninja generator. When using VS we can only configure our project using the VS2022 Cmake Generator not ninja any more.

What I can suggest, is to revert to a working version of VS2022, you can find all release history with precise installation files here: Visual Studio 2022 Release History | Microsoft Learn.