Compilation databases: reproduce the failing translation unit before changing headers

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

article · en · 지식 기준일 2026-09-22 · 변경일 2026-09-24, 리비전 2 · reviewed (검토 기록됨 2026-09-24)

Use the real compile command and working directory to distinguish source defects from editor configuration errors.

What it is

With a supported generator, CMake's CMAKE_EXPORT_COMPILE_COMMANDS produces compile_commands.json containing compiler invocations for translation units. The documentation limits this feature to Makefile and Ninja generators and notes difficulties with unity builds. The database describes compilation commands; it is not a claim that the whole application has linked or run. CMake compilation database

Why it matters

An agent can make a correct file incorrect by responding to diagnostics produced with the wrong include path, language mode or macro set. Before adding compatibility branches, compare the diagnostic context with the command used by the build. This proposed method treats compiler context as evidence.

How to apply

Identify the specific source file and active build configuration. Locate its entry in the compilation database and read its working directory and compiler arguments.
Regenerate the database through the project's normal CMake configuration after changing toolchains or relevant options. Avoid hand-editing the generated file as a lasting fix.
Reproduce the translation-unit diagnostic from the recorded directory in a disposable build environment. Preserve argument boundaries when handling paths with spaces.
Compare editor settings with that command: include directories, generated headers, language standard and definitions are useful first candidates. Record any deliberate difference instead of assuming both tools use identical defaults.
After correcting the context, rerun the targeted check and the project's actual build. If the diagnostic remains, reduce the source problem while preserving the same relevant flags.

Pitfalls

A header may be included by several translation units with different macros; one inferred command cannot represent every use. Multiple entries for a file also require selecting the intended configuration. Unity builds may combine source files in ways a per-file tool does not model. Do not describe a clean editor panel as a successful build or a compilation database as a complete dependency lockfile.

범위와 근거

Original synthesis from the cited primary documentation, with proposed diagnostic and verification steps. No benchmark, experiment or field result is claimed; unreviewed AI-assisted contribution.

지식 기준일: 2026-09-22. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-24에 리비전 2을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: New English original; AI-assisted and unreviewed. Proposed checks have not been executed for this article.

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.