C/C++ (CMake + CTest) support: tracking issue

Ouverte
#138 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
c, cmake, cpp, typescript

Piste de recherche

Read the adapter guide and the Rust model at src/repo/adapters/rust.ts, then inspect adapter registration in src/repo/adapters/index.ts and the release boundary. The tracking issue lists independent steps; choose an unblocked one and keep unsupported CMake forms in blockers so the full suite runs. Done for a step means its behavior is implemented and covered, with the final replay step requiring a public CMake repository and a published report.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

adapter enhancement help wanted

DiffCI works out what a change needs from CI, starting with the tests it affects, so AI coding agents (and people) can run them before pushing. It supports JS/TS, Vue, Go, Maven, pytest and Cargo today. C and C++ are open for contributors and design partners.

First supported setup: a CMake project whose tests are registered with CTest (add_test, or gtest_discover_tests / catch_discover_tests), run with ctest. Selection happens at the CMake target level first.

Steps (each is one PR; take any that are unblocked):

  • Map source files to targets from literal file lists in add_library / add_executable / target_sources
  • Build the target graph from target_link_libraries and add_subdirectory
  • Follow #include "..." to map changed headers to the targets that include them (quoted includes resolved against target_include_directories)
  • Map test targets to CTest tests and generate ctest -R '<regex>' (or ctest -L) commands for the selected tests
  • Fall back with a reason on what the graph can't see: file(GLOB ...), generator expressions, variables built in loops or conditions, include() of custom .cmake modules, configure_file outputs, macro-driven or generated sources, CMakeLists.txt / toolchain / preset changes
  • Register the adapter in REPOSITORY_ADAPTERS (src/repo/adapters/index.ts) and add it to the release boundary
  • Replay on one public CMake repository and publish the report

Ground rules

  • CMake files are code, not data. Read them statically and only trust simple, recognisable forms; anything else records a blockers entry and DiffCI runs the full suite. An empty graph must never look like "nothing affected".
  • Plain Makefiles, Meson and autotools are out of scope for the first version; they should be detected and fall back to the full suite with a clear reason. Bazel C/C++ is covered by the Bazel tracking issue.
  • Don't run CMake to fill gaps; the engine doesn't install or run project tooling.
  • Read the adapter guide first; the Rust adapter (src/repo/adapters/rust.ts) is a close model for target-level selection.
  • Discuss design questions here, so every step stays consistent.

Using C or C++ and want to help, or have a repository we could test against? Say so below. 👍 this issue if you'd use it; reactions on the language tracking issues decide what comes after.

Langage dominant
TypeScript
Étoiles
0
Forks
4
Merge moyen
18 h 41 min
PR mergées (30 j)
48

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de DiffCI/core

Toutes les issues de DiffCI/core

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.