CDT Call October 2025

[jonahgraham]

Our next CDT Call will be October 8th 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

• Location: 💻 Zoom Meeting (full details below)
• Date: October 8 2025 11:00 AM Eastern Time (US and Canada) (Calendar/ICS) (world clock)
• Agenda

1. Welcome
2. Status of 2025-12 and upcoming CDT and CDT LSP releases
3. LSP editor for Makefile projects. Related to Build using compile_commands.json to automatically assign language for discovered sources #1321
4. How to proceed with Makefile projects How to proceed with Makefile projects #1305
5. Please clarify status of Fix for the compiler path in compile_commands.json file #1138. Is @alicetrifu still working on it?
6. Related to How to proceed with Makefile projects #1305, documentation refactoring.
7. Processing the recent CDT parser PRs - Re-affirm (and document properly): Adopt special review process officially #1347 (comment)
8. Set CC and CXX environment variables for clang toolchain #1169 (comment)
9. Remove ToggleInstructionStepModeCommand from Run Menu and Main Toolbar. #1143 (comment)
10. Any other business?

• Contact: [email protected] 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

Attendees

Minutes

see #1340 (comment)

[ghentschke]

Unfortunately I cannot attend tomorrow. I am currently working on cdt-lsp bug fixes eclipse-cdt/cdt-lsp#516 and eclipse-cdt/cdt-lsp#550
They have to be fixed in LSP4E.
IMO the PR #1138 is important for Makefile projects, as the current compile_commands.json generation is somehow faulty. It should be fixed for Eclipse 2025-12.

[jonahgraham]

Unfortunately I cannot attend tomorrow. I am currently working on cdt-lsp bug fixes eclipse-cdt/cdt-lsp#516 and eclipse-cdt/cdt-lsp#550
They have to be fixed in LSP4E.

Sorry you cannot attend - thanks for sharing the significant progress you have made on resolving some very tricky issues.

IMO the PR #1138 is important for Makefile projects, as the current compile_commands.json generation is somehow faulty. It should be fixed for Eclipse 2025-12.

I have rebased and re-reviewed this and I think it is ready to go, feel free to submit it if you agree.

[jonahgraham]

I have rebased and re-reviewed this and I think it is ready to go, feel free to submit it if you agree.

I have merged this just now.

[betamaxbandit]

If there is time, I'd like to discuss ...

clangd Protocol extensions

I'm interested in the work done by @travkin79 in the following:

eclipse-cdt/cdt-lsp#253

https://clangd.llvm.org/extensions#ast

eclipse-cdt/cdt-lsp#256

I'm just familiarising myself with LSP and would like to try some examples/experiments of using ClangdLanguageServer.getAst and ClangdLanguageServer.getSymbolInfo from a locally installed version of clangd.

I'm wondering what's the best way to get started?

[travkin79]

Hi @betamaxbandit,

I'm wondering what's the best way to get started?

I guess, you're looking for something like this:
eclipse-cdt/cdt-lsp#256 (comment)

[travkin79]

Hi @jonahgraham,
Is there any chance that someone could help finishing the following clangd PR draft in order to add access modifiers and other tags to the LSP?
llvm/llvm-project#113669

As soon as it is finished and merged, we could finish all related LSP4J, LSP4E PRs (eclipse-lsp4j/lsp4j#856, eclipse-lsp4e/lsp4e#1149) and finally finish this LSP spec PR:
microsoft/language-server-protocol#2003

[jonahgraham]

I brought this up at the CDT call - there were no immediate volunteers, sorry 😞

[ghentschke]

Is there any chance that someone could help finishing the following clangd PR draft in order to add access modifiers and other tags to the LSP?

What about the pull request proposal mentioned in llvm/llvm-project#113669 ?

[jonahgraham]

113669 is the PR we talked about in the call. No one volunteered to jump in on it.

[travkin79]

Hi @jonahgraham,
Thank you for bringing this up.

[jonahgraham]

Minutes

• Status of 2025-12 and upcoming CDT and CDT LSP releases

No particular discussion - many of the issues are discussed below.

• LSP editor for Makefile projects. Related to Build using compile_commands.json to automatically assign language for discovered sources #1321

Options discussed including using using the same Makefile output parser to directly generate compile_commands.json (which solves the issue for Makefile projects only) or "reading" Path and Symbols database to populate a compile_commands.json (which could allow generating compile_commands.json for all build tools that CDT currently supports)

Documentation needed - for example, manage make's generate compile_commands.json is under(un)documented.

Third party tools, such as Bear or compiledb can be used to generate compile_commands.json.

Action #1 could be to give an error marker if compile_commands.json is not present and then use that to direct users how to create compile_commands.json?

• How to proceed with Makefile projects How to proceed with Makefile projects #1305

Erwin showed demo that renamed "C Managed Build" -> "Classic Makefile C Project". This lead to lots of discusion that will attempt to be continued in #1305. Erwin will put screenshots in #1305

There may be vendor documentation that needs updating based on the change in names. This should be documented clearly in N&N, especially for vendors.

• Please clarify status of Fix for the compiler path in compile_commands.json file #1138. Is @alicetrifu still working on it?

Now merged.

• Related to How to proceed with Makefile projects #1305, documentation refactoring.

Except for getting started - rest of documentation is very out of date as everything else refers only to managed build.

• Processing the recent CDT parser PRs - Re-affirm (and document properly): Adopt special review process officially #1347 (comment)

No objections from everyone on the call to reaffirming the policy change which will be merged soon and allow merging of all related PRs.

• Set CC and CXX environment variables for clang toolchain #1169 (comment)

John D + John M will see the current change to completion as soon as practicable and leave any additional complications and special cases for future issues. They plan to meet after this call to discuss further and share the results in #1169

• Remove ToggleInstructionStepModeCommand from Run Menu and Main Toolbar. #1143 (comment)

Is this still needed for #1221?

Add N&N to last release about #1221 being removed.

• clangd Protocol extensions

travkin79 has responded on the call discussion - Jonah recommended starting a new discussion on this topic.

Links for how clangd is installed on github actions and on Jenkins