diff options
| author | fanquake <fanquake@gmail.com> | 2022-04-05 09:18:20 +0100 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2022-04-05 09:33:58 +0100 |
| commit | 0baf6aded5fa1f98c95cd6bb54089f4412aa6768 (patch) | |
| tree | 41fd259520f7d1f980fa158abf69414bc8c3285c /src/Makefile.test.include | |
| parent | 44e7d6d6ddad90dbbe291db012285d911050a9bd (diff) | |
| parent | 7b00595d335915dc2bf856e3569115996381a402 (diff) | |
| download | bitcoin-0baf6aded5fa1f98c95cd6bb54089f4412aa6768.tar.xz | |
Merge bitcoin/bitcoin#24391: build: stop overriding user autoconf flags
7b00595d335915dc2bf856e3569115996381a402 build: stop overriding user CXXFLAGS (fanquake)
3e2ef23c3e838acbc2cba7d26a36a4c6008faa24 build: stop overriding user LDFLAGS (fanquake)
35c3fd43c3d5a1c7e1b32865ddc2b046ad448986 build: stop overriding user CPPFLAGS (fanquake)
bc7cc576072703e4521844b949af5ce7d7e4722a doc: explain why we clear CXXFLAGS with enable-debug (fanquake)
Pull request description:
Historically our build system has hijacked `CXXFLAGS` and friends, and this has always been a source of complaints from users and developers. With this PR, we move away from using `CXXFLAGS`, `CPPFLAGS` and `LDFLAGS`, and instead use `CORE_*FLAGS` variables for our flags / options, leaving autoconfs `FLAG` vars to the user.
Note that there are currently two cases where we will at least clear `CXXFLAGS` (if not alreaddy overridden by the user), when doing debugging or when coverage is enabled, to avoid Autoconfs `-g -O2` CXXFLAG default.
ACKs for top commit:
hebasto:
ACK 7b00595d335915dc2bf856e3569115996381a402
Tree-SHA512: bda936a7aa8f98a1bf1552306845cb4bbab54e19a7a0b9ce3210e10fef70db146e9fe42a0cc8c50b2908506771b5b96f39c334e41323b70ec878e4010373096c
Diffstat (limited to 'src/Makefile.test.include')
0 files changed, 0 insertions, 0 deletions