mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-01-25 10:43:19 -03:00
71383f2fad
Don't enable `-Werror` (in the CI) for compilers at least older than our current release compiler (GCC 10). It provides little-to-no value, other than turning compiler bugs & false positives into build failures, and we aren't going to mutate perfectly fine/working code, for the sake of avoid a warning that shouldn't even exist. I also do not see the point of playing whack-a-mole and turning off various warnings/trying to further work around the broken compiler, just to acheive warningless builds for the sake of warningless builds. One anecdote from "How SQLite Is Tested": > Static analysis has found a few bugs in SQLite, but those are the > exceptions. More bugs have been introduced into SQLite while trying > to get it to compile without warnings than have been found by static > analysis. https://www.sqlite.org/testing.html. |
||
|---|---|---|
| .. | ||
| 00_setup_env.sh | ||
| 00_setup_env_android.sh | ||
| 00_setup_env_arm.sh | ||
| 00_setup_env_i686_centos.sh | ||
| 00_setup_env_i686_multiprocess.sh | ||
| 00_setup_env_mac.sh | ||
| 00_setup_env_mac_native_arm64.sh | ||
| 00_setup_env_native_asan.sh | ||
| 00_setup_env_native_fuzz.sh | ||
| 00_setup_env_native_fuzz_with_msan.sh | ||
| 00_setup_env_native_fuzz_with_valgrind.sh | ||
| 00_setup_env_native_msan.sh | ||
| 00_setup_env_native_nowallet_libbitcoinkernel.sh | ||
| 00_setup_env_native_qt5.sh | ||
| 00_setup_env_native_tidy.sh | ||
| 00_setup_env_native_tsan.sh | ||
| 00_setup_env_native_valgrind.sh | ||
| 00_setup_env_s390x.sh | ||
| 00_setup_env_win64.sh | ||
| 04_install.sh | ||
| 05_before_script.sh | ||
| 06_script_a.sh | ||
| 06_script_b.sh | ||
| wrap-qemu.sh | ||
| wrap-valgrind.sh | ||
| wrap-wine.sh | ||
| wrapped-cl.bat | ||