CDT Call February 2025

[jonahgraham]

Our next CDT Call will be February 12th at 11am Ottawa time. Please make a comment to add suggestions for discussion topics, or come along to the call and we can discuss anything in "Any other business" section. Everyone is welcome.

Call Information

Call Information and Agenda

• Location: 💻 Zoom Meeting (full details below)
• Date: February 12, 2024 11:00 AM Eastern Time (US and Canada) (Calendar/ICS) (world clock)
• Agenda

1. Welcome
2. Actions from last meeting
3. SonarQube for Eclipse (formerly SonarLint) alongside Eclipse CDT #988
4. CDT 12.0 planning
5. Any other business?

• Contact: cdt-dev@eclipse.org or start a discussion topic
• Reference: Previous and future meetings (older call notes are located here)

Connection Details

Join Zoom Meeting
https://eclipse.zoom.us/j/545364607
Meeting ID: 545 364 607
Passcode: 196590
Dial by your location find your local number: https://eclipse.zoom.us/u/acMY3kyoJW

Minutes

• @thahnen gave a presentation about the SonarQube plug-in and its impact on CDT

  • A recording was made of this portion of the call, saved on Zoom here. Passcode: 2@s!012L
  • @thahnen made some notes and added extra info in a detailed comment CDT Call February 2025 #996 (reply in thread)

• @jonahgraham discussed how to present CDT LSP to new users - see updates that will be posted in #968. The short summary is that when a user opens the CEditor, there is a new ribbon at the top that encourages them to try the new C/C++ editing experience:

• @jld01 plans to look at updating before you begin help page to include some or multiple of these ideas:
  • using winget to install tools
  • using msys2 to install tools
  • instructions/links for installing clangd (necessary for the new C/C++ editing experience in CDT LSP)
• @jld01 plans to look into the CDT LSP icons located here: https://github.com/eclipse-cdt/cdt-lsp/tree/main/bundles/org.eclipse.cdt.lsp/icons

Reminders on important upcoming dates:

• Next week is M3 week. CDT 12 M3 must be contributed no later than EOD Wednesday 19 Feb. This is the last chance for very disruptive changes. Eclipse IDE for C/C++ users 2025-03 M3 will be available on Friday 21st at https://www.eclipse.org/downloads/packages/release/2025-03
• Week after is RC1, CDT 12 RC1 must be contributed no later than EOD Wednesday 26 Feb. This is the last chance for anything other than fixes and help changes. Eclipse IDE for C/C++ users 2025-03 M3 will be available on Friday 28th at https://www.eclipse.org/downloads/packages/release/2025-03
• Week after is RC2, CDT 12 RC2 must be contributed no later than EOD Wednesday 5 Mar. This is the last chance for fixes and help changes. Eclipse IDE for C/C++ users 2025-03 release will be available on March 12 (test builds available on March 7th)

• Next CDT call is March 12 CDT Call March 2025 #1085 Note the meeting is an hour earlier for some people due to daylight savings time change

[jonahgraham]

@thahnen I have added discussions to next month's agenda here

[jonahgraham]

Here are answers to what I know - feel free to ask specific questions (as new discussions perhaps linked from here so they don't get lost in the noise of this discussion)

an API for getting the Compilation Database would be great, for now there are generic places to look at (e.g. Project<Configuration>\compile_commands.json)

CDT LSP had to solve this problem and the heuristic is here in the code.

I am open to new API, but I don't know what that would look like or where it would live.

Or at least an API to check whether Compilation Database generation is enabled in that project?

No API, but for managed build (MBS) projects you can check the preference, see this method

Might be worth checking out to create a Compilation Database Generator for these kind of projects, all other project types available with Eclipse CDT as far as I know (CDT managed build, CMake, GNU Autotools, Meson, ...) can generate such a compile_commands.json when the preference is set.

• For MBS (aka CDT managed build) the option is as above.
• For CMake we pass it -DCMAKE_EXPORT_COMPILE_COMMANDS=ON to get compile_commands.json (unconditionally here)
• For Meson, autotools and other external build systems we rely on them to generate the compile_commands.json, but we don't currently consume them in CDT, nor turn them on. We should and I would certainly review patches for that
• For Standard Make projects, we can use the scanner information we already calculate to generate a compile_commands.json. Patches also welcome for this. (if we do this for standard make, we should be able to do it for anything)

[jonahgraham]

@thahnen see above some answers.

And here is one question. I assume that Sonar's analysis tool runs the compiler specified in the compile_commands.json file to get the compiler's internal includes and defines in a similar way that clangd does. Can you confirm that? For clangd we enable --query-driver so that clangd has permission to start the compiler driver for such info.

See this GUI:

[jonahgraham]

I was asking on the call whether you ran the build under a tool to determine what is happening. What prompted that question was the Bear tool which generates compile_commands.json for arbitrary build systems.

[thahnen]

Hi @jonahgraham, I forwarded that question to my colleagues directly working with the analyzer as this is information I'm sadly not familiar with. I guess someone will answer you soon.

For the rest of your replies: Thank you very much, this is very valuable information to me!

[thahnen]

Hey, I can provide you only a short answer to your question: Yes, the CFamily analyzer for C/C++ uses something similar to clangd's --query-driver.
More information I cannot provide to you for now, sorry (the analyzer itself is closed source).