C/C++ tools not recognised: cmake-format/gersemi, astyle, Coverity Scan, scan-build as an analyzer job, OpenCppCoverage, uncrustify, tools driven by `zig build`, MinGW hardening flags

Aperta
  • Qualcosa non va?
#282 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cmake, cpp, python
Ambito
tooling

Direzione di ricerca

Start in the project_validator/ package, where the grep -rn cmake-format project_validator/ check finds nothing, and find how the C/C++ profile detects formatters, static analyzers, coverage tools and hardening flags. Each listed tool needs a recognition rule and a note or WARN credit, with the nlohmann astyle message corrected. Done means the corpus cases named in the issue now produce the expected results, and the existing tests still pass.

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

Descrizione

fmt's CI job formats CMake files with cmake-format and fails on a diff (invisible); nlohmann/json defines its style in tools/astyle/.astylerc and CI fails when astyle changes the headers ("formatting is not defined" is wrong even if astyle stays unsupported); dbus-broker, nlohmann and glib run Coverity Scan jobs; glib and neovim run the Clang Static Analyzer (scan-build) as a CI job ("no static analyzer runs"); cmake_template and Catch2 run OpenCppCoverage on Windows (--export_type cobertura:); neovim runs clang-tidy and uncrustify through zig build targets in build.zig, and emmylua_check for Lua types; glfw links the MinGW equivalents of /DYNAMICBASE/DEP.

Evidence from the corpus audit

fmtlib/fmt, cpp-best-practices/cmake_template / code-formatting (cmake-format)
  • kind: UNSUPPORTED
  • actual: no mention; fmt's CI job that formats CMake files and fails on a diff is invisible.
  • expected: cmake-format (cmakelang) / gersemi recognised as CMake-file formatters, at least as evidence.
  • evidence: fmt .github/workflows/lint.yml:33 cmake-format:; :43-45: find . -name CMakeLists.txt -o -name '*.cmake' | \ / xargs cmake-format -i / git diff --exit-code; fmt .cmake-format; cmake_template
    .cmake-format.yaml. grep -rn cmake-format project_validator/ finds nothing.
  • repro: n/a (gap)
  • confidence: high
nlohmann/json / code-formatting (astyle)
  • kind: UNSUPPORTED
  • actual: FAIL: "C/C++: no clang-format configuration found; formatting is not defined"
  • expected: the project defines its style in tools/astyle/.astylerc and CI fails when astyle changes the
    amalgamated headers (check_amalgamation.yml -> ci_test_amalgamation); "formatting is not defined" is wrong even
    if astyle stays unsupported.
  • evidence: cmake/ci.cmake:446: COMMAND venv_astyle/bin/astyle --project=tools/astyle/.astylerc --suffix=none ${include_dir}/json.hpp ...; Makefile:90: ASTYLE=tools/astyle/venv/bin/astyle; .github/workflows/check_amalgamation.yml.
  • repro: n/a (gap)
  • confidence: high
bus1/dbus-broker, nlohmann/json / static-analysis (Coverity Scan)
  • kind: UNSUPPORTED
  • actual: dbus-broker "C/C++: no static analyzer runs"
  • expected: Coverity Scan is a static analyzer common in C projects; a scheduled make coverity-scan /
    cov-build job deserves at least a WARN-level credit.
  • evidence: dbus-broker .github/workflows/coverity.yml:48: run: make coverity-scan; :51: run: make coverity-upload
    (targets in the top-level Makefile); nlohmann README shows a Coverity Scan badge (status-badges names it).
  • repro: n/a (gap)
  • confidence: medium
cpp-best-practices/cmake_template, catchorg/Catch2 / coverage (OpenCppCoverage)
  • kind: UNSUPPORTED
  • actual: no mention of the Windows coverage runs (cmake_template PASSes on gcovr anyway; Catch2's appveyor is
    heuristic).
  • expected: OpenCppCoverage (--export_type cobertura:) recognised as a Windows coverage tool.
  • evidence: cmake_template .github/workflows/ci.yml:185: OpenCppCoverage.exe --export_type cobertura:coverage.xml --cover_children -- ctest -C ${{matrix.build_type}}; Catch2 appveyor.yml:22:
    .\tools\misc\installOpenCppCoverage.ps1.
  • repro: n/a (gap)
  • confidence: medium
GNOME/glib, neovim/neovim / static-analysis (scan-build, Coverity)
  • kind: UNSUPPORTED
  • actual: glib FAIL "C/C++: no static analyzer runs"; neovim FAIL "clang-tidy is configured (.clang-tidy) but does not run"
  • expected: note only: both run the Clang Static Analyzer (scan-build) as a CI job, and glib has a Coverity job; the C/C++ profile accepts only clang-tidy and cppcheck.
  • evidence: glib .gitlab-ci.yml:1140: - SCANBUILD="$(pwd)/.gitlab-ci/scan-build.sh" ninja -C _scan_build scan-build; :1175: "${HOME}"/cov-analysis-linux64-*/bin/cov-build --dir cov-int meson compile -C _coverity_build; neovim .github/workflows/test.yml:135: - run: cmake --build build --target clang-analyzer.
  • repro: n/a (gap)
  • confidence: high
neovim/neovim / tools driven by zig build, uncrustify, emmylua
  • kind: UNSUPPORTED
  • actual: static-analysis "clang-tidy is configured (.clang-tidy) but does not run"; code-formatting "C/C++: .clang-format is defined but CI does not run clang-format"; type-checking "Lua: lua-language-server is configured (.luarc.json) but does not run"
  • expected: note only: clang-tidy and the C formatter (uncrustify, not clang-format) run through zig build targets defined in build.zig; Lua type checking runs with emmylua_check (emmylua-check target, .emmyrc.json), not lua-language-server.
  • evidence: .github/workflows/test.yml:61: run: zig build lintc-clang-tidy $OPTS; :65: run: zig build lintc-uncrustify $OPTS; :109: run: cmake --build build --target emmylua-check; src/nvim/CMakeLists.txt:966-967: COMMAND ${UNCRUSTIFY_PRG} / FLAGS -c ${UNCRUSTIFY_CONFIG} -q --check; .emmyrc.json; build.zig.
  • repro: n/a (gap; build.zig needs a Zig evaluator)
  • confidence: high
glfw/glfw / hardening (MinGW link flags)
  • kind: UNSUPPORTED
  • actual: FAIL: "no hardening options found; ... /DYNAMICBASE, /CETCOMPAT"
  • expected: note only: the MinGW equivalents of /DYNAMICBASE and DEP are linked when available.
  • evidence: src/CMakeLists.txt:300: target_link_libraries(glfw PRIVATE "-Wl,--nxcompat"); :309: target_link_libraries(glfw PRIVATE "-Wl,--dynamicbase"); :318: target_link_libraries(glfw PRIVATE "-Wl,--high-entropy-va").
  • repro: n/a (gap)
  • confidence: low

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

Lingua principale
Python
Stelle
4
Fork
1
Merge medio
10h 41m
PR unite (30g)
79

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 cpp-best-practices/project_validator

Tutte le issue di cpp-best-practices/project_validator

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.