Skip to content

Commit 43e287b

Browse files
committed
Merge bitcoin#31892: build: remove ENABLE_HARDENING condition from check-security
113a7a3 build: remove ENABLE_HARDENING cond from check-security (fanquake) Pull request description: This check is only used in release builds, where hardening should always be enabled. I can't think of a reason we'd want to silently skip these checks if hardening was inadvertently disabled. ACKs for top commit: maflcko: lgtm ACK 113a7a3 TheCharlatan: ACK 113a7a3 hebasto: ACK 113a7a3. Tree-SHA512: 46217e8ab238e23374d758b12e5b6bdc22353d8bf272aa0d2260cdea023b5b80aba972dccaa0a4fb8da21c8c665991848f7fd79966d20ac2489d499c68d95639
2 parents 63d625f + 113a7a3 commit 43e287b

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

cmake/module/Maintenance.cmake

+5-9
Original file line numberDiff line numberDiff line change
@@ -35,15 +35,11 @@ function(add_maintenance_targets)
3535
VERBATIM
3636
)
3737

38-
if(ENABLE_HARDENING)
39-
add_custom_target(check-security
40-
COMMAND ${CMAKE_COMMAND} -E echo "Checking binary security..."
41-
COMMAND ${PYTHON_COMMAND} ${PROJECT_SOURCE_DIR}/contrib/devtools/security-check.py ${executables}
42-
VERBATIM
43-
)
44-
else()
45-
add_custom_target(check-security)
46-
endif()
38+
add_custom_target(check-security
39+
COMMAND ${CMAKE_COMMAND} -E echo "Checking binary security..."
40+
COMMAND ${PYTHON_COMMAND} ${PROJECT_SOURCE_DIR}/contrib/devtools/security-check.py ${executables}
41+
VERBATIM
42+
)
4743
endfunction()
4844

4945
function(add_windows_deploy_target)

0 commit comments

Comments
 (0)