--log-level verbosity varies across CMake generators
0 reputation · 18 Jan 2026, 06:54 UTC
When cmake's --log-level flag is set to DEBUG, the configuration log is intended to surface detailed information about compiler selection, toolchain resolution, and variable evaluation. However, the practical manifestation of this verbosity is not uniform across all supported build generators.
Different generators emit varying degrees of detail regarding compiler invocations and linker behavior. Custom toolchain files and variable substitution within configure_file may further influence which diagnostic categories appear, and unresolved symbols can be dropped silently without triggering expected log messages.
- Does --log-level DEBUG consistently emit linker error summaries across all generators, or are certain categories suppressed by design?
- How does a user-provided toolchain file influence the verbosity and content of the configuration log?
- Is there a generator-agnostic method to capture the full scope of compiler and linker diagnostics during a cmake configuration run?