Details
Details
- Reviewers
deadalnix - Group Reviewers
Restricted Project - Commits
- rSTAGINGa423ecd14cd9: [CMAKE] Harden the executables
rABCa423ecd14cd9: [CMAKE] Harden the executables
# Linux mkdir buildcmake && cd buildcmake cmake -GNinja .. ninja -v ../contrib/devtools/security-check.py src/bitcoind
The security-check script should output no error.
# Win32 rm -rf * cmake -GNinja .. -DBUILD_BITCOIN_SEEDER=OFF \ -DCMAKE_TOOLCHAIN_FILE=../cmake/platforms/Win32.cmake ninja -v ../contrib/devtools/security-check.py src/bitcoind.exe
The security-check script should output no error.
# Win64 rm -rf * cmake -GNinja .. -DBUILD_BITCOIN_SEEDER=OFF \ -DCMAKE_TOOLCHAIN_FILE=../cmake/platforms/Win64.cmake ninja -v ../contrib/devtools/security-check.py src/bitcoind.exe
The security-check script should output no error.
OSX build is not working yet with CMake.
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- cmake_hardening_all
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 5242 Build 8547: Bitcoin ABC Buildbot (legacy) Build 8546: arc lint + arc unit
Event Timeline
src/CMakeLists.txt | ||
---|---|---|
66 ↗ | (On Diff #7698) | This is what autotools do, but I agree this is weird. I can include C if you are comfortable with it. |
src/CMakeLists.txt | ||
---|---|---|
76 ↗ | (On Diff #7701) | I see 3 ways of linking against libssp for all the executables:
|
src/CMakeLists.txt | ||
---|---|---|
76 ↗ | (On Diff #7701) | Using link libraries is the right thing to do. |