summaryrefslogtreecommitdiffstats
path: root/Source/cmTryCompileCommand.cxx
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2023-01-13 16:55:56 (GMT)
committerBrad King <brad.king@kitware.com>2023-01-16 22:18:07 (GMT)
commit48292c8624b901a842b6d4f8a88ca00f898e5639 (patch)
tree3fe69130b088d51d082fb842d6d3688c874455a9 /Source/cmTryCompileCommand.cxx
parentd4bf7d80c618930e6b88c35d271a5b0a0656bb7b (diff)
downloadCMake-48292c8624b901a842b6d4f8a88ca00f898e5639.zip
CMake-48292c8624b901a842b6d4f8a88ca00f898e5639.tar.gz
CMake-48292c8624b901a842b6d4f8a88ca00f898e5639.tar.bz2
try_compile: Record stack of in-progess checks in configure log
Many `try_compile` and `try_run` calls occur inside check modules between `message(CHECK_START)` and `message(CHECK_{PASS,FAIL})` pairs. Add a field to configure log entries to report this context. Issue: #23200
Diffstat (limited to 'Source/cmTryCompileCommand.cxx')
-rw-r--r--Source/cmTryCompileCommand.cxx1
1 files changed, 1 insertions, 0 deletions
diff --git a/Source/cmTryCompileCommand.cxx b/Source/cmTryCompileCommand.cxx
index ebbb4f2..789ffe9 100644
--- a/Source/cmTryCompileCommand.cxx
+++ b/Source/cmTryCompileCommand.cxx
@@ -27,6 +27,7 @@ void WriteTryCompileEvent(cmConfigureLog& log, cmMakefile const& mf,
if (log.IsAnyLogVersionEnabled(LogVersionsWithTryCompileV1)) {
log.BeginEvent("try_compile-v1");
log.WriteBacktrace(mf);
+ log.WriteChecks(mf);
cmCoreTryCompile::WriteTryCompileEventFields(log, compileResult);
log.EndEvent();
}