CMake cross-compilation probes: distinguish compiling, linking and running
この記事はまだ日本語では提供されていません。原文を表示しています。
Diagnose toolchain checks by identifying which machine must compile, link or execute each probe.
What it is
Cross-compilation separates the machine running the build tools from the machine that will run the output. CMake's toolchain documentation describes target search roots and CMAKE_FIND_ROOT_PATH_MODE settings. For toolchains that cannot link a normal executable during compiler checks, CMAKE_TRY_COMPILE_TARGET_TYPE can request a static-library check instead. CMake toolchains manual
Why it matters
A failed configuration probe is not automatically evidence that the target lacks a feature. The probe may have found a host library, required a target execution environment, or omitted a linker script. Agents should identify the failed stage before replacing a measured capability with a guessed cache value.
How to apply
- Write down the build host, target architecture, compiler, sysroot and intended execution environment. Keep the toolchain file with the build instructions.
- Read the exact failing probe and classify it as a compile check, link check or execution check. Capture its command and diagnostic, excluding credentials and unrelated environment variables.
- Confirm that libraries and headers come from the target tree, while code generators that must run during the build are executable on the host.
- If a compiler check cannot link without platform-specific support, consider a static-library probe only for the claim that compilation is sufficient to establish. Do not relabel it as a successful executable-link test.
- Propose a target smoke test that exercises the originally questioned feature. Use an authorized target or documented emulator and record separately whether execution was possible.
Pitfalls
A compiler accepting a declaration does not establish runtime availability. Preseeding a cache answer can be appropriate when derived from reliable target evidence, but record its origin and scope. Changing the sysroot or compiler can invalidate old answers. Start a separate build tree for a changed toolchain rather than treating unrelated cached probe results as portable facts.
範囲と根拠
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。状態：unreviewed（レビュー記録なし） — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。
出典
- CMake toolchains manual — 2026-09-23 確認：到達可能、引用箇所あり
帰属とライセンス
- Account External coding curation authors (57eb56c9)
- Written with Codex, an AI coding agent, at the site operator's request; original synthesis, sources credited separately.
最新の変更： New English original; AI-assisted and unreviewed. Proposed checks have not been executed for this article.
オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。