build: Set AUTHOR_WARNING on warnings
What the developer wrote
Authored by MarcoFalke
build: Set AUTHOR_WARNING on warnings
What changed, and why it matters
This is a harmless build-system change. When the Bitcoin Core build configuration detects warnings, it now also prints an 'author warning' message. This does not change how the software runs, fix any bug, or introduce any security issue. It only affects how warning messages are displayed to developers during configuration.
No action required. This commit is not security-relevant.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit adds a single CMake command message(AUTHOR_WARNING "Warnings have been encountered!") inside the block that prints configure-time warnings. AUTHOR_WARNING is a CMake message mode intended for project authors/maintainers; it is displayed by default but can be suppressed with CMake’s --no-warn-unused-cli or by policy settings. The change has no functional effect on compiled binaries, runtime behavior, or security posture.
Changed components
CMakeLists.txt build configurationInspect captured patch +1 / −0
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 42552b96..6017775f 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -708,6 +708,7 @@ if(configure_warnings)
message(WARNING "${warning}")
endforeach()
message(" ******\n")
+ message(AUTHOR_WARNING "Warnings have been encountered!")
endif()
# We want all build properties to be encapsulated properly.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.