mcpp projects: no root compile_commands.json by default; read mcpp's result record for fallback and refresh

Aperta
  • Qualcosa non va?
#71 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
backend-api-design, developer-experience

Direzione di ricerca

Read src/project/mcpp.cppm at McppProvider::describe and the referenced mcpp design sections §7 and §5.2. Trace how the fallback selects a compilation database and how build refresh is forwarded by the editor extension; check the CLion e2e coverage. Done means the result record pointer is preferred, the root database remains a compatibility fallback, and the proposed refresh and CLion behavior are covered.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Context

The next mcpp release changes two things mcppls touches on mcpp projects (design: mcpp/.agents/docs/2026-10-26-control-contract-runtime-and-ide-ecosystem-design.md, §7 and §5.2):

  1. The project-root compile_commands.json is no longer written by default. It becomes opt-in through [build] compile_commands = "<path>" in mcpp.toml (or a default in ~/.mcpp/config.toml). An existing root copy is no longer updated, and mcpp prints a one-time note. The per-configuration database (target/<triple>/<fp>/compile_commands.json) stays.
  2. mcpp writes a result record after every build (target/<triple>/<fp>/result.json, kind mcpp.result), plus a project-level pointer target/.last-result.json naming the most recent configuration. The record carries the configuration's compile database path, the diagnostics, and the artifacts.

What this means for mcppls

  • Fallback path. McppProvider::describe falls back to a leftover root compile_commands.json when mcpp cannot be asked (src/project/mcpp.cppm:41). After the change, that file is usually absent. The fallback should read the database named by target/.last-result.json first, and the root file only when the pointer is missing (older mcpp).
  • Refresh after a build. Watching target/.last-result.json (written by atomic rename) tells mcppls that a build finished, whoever ran it: a terminal, an agent's shell, or an IDE. Today the refresh is forwarded by the editor extension.
  • CLion. Without a root compile_commands.json, CLion no longer loads an mcpp project as a Compilation Database workspace, so ClionModel no longer treats it as CLion's and mcppls starts by default. No code change is expected; an e2e assertion would pin it.

Nothing breaks immediately: the primary path (mcpp emit build-database) is unchanged. This issue tracks adopting the result record when that mcpp release ships.

Lingua principale
C++
Stelle
25
Fork
2
Merge medio
21h 5m
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Sunrisepeak/mcpp-language-server

Tutte le issue di Sunrisepeak/mcpp-language-server

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.