bitcoin/ci/test/00_setup_env_native_nowallet_libbitcoinkernel.sh

#!/usr/bin/env bash
#
# Copyright (c) 2019-2022 The Bitcoin Core developers
# Distributed under the MIT software license, see the accompanying
# file COPYING or http://www.opensource.org/licenses/mit-license.php.

export LC_ALL=C.UTF-8

export CONTAINER_NAME=ci_native_nowallet_libbitcoinkernel
export CI_IMAGE_NAME_TAG="ubuntu:20.04"
# Use minimum supported python3.8 and clang-10, see doc/dependencies.md
export PACKAGES="python3-zmq clang-10 llvm-10 libc++abi-10-dev libc++-10-dev"
export DEP_OPTS="NO_WALLET=1 CC=clang-10 CXX='clang++-10 -stdlib=libc++'"
export GOAL="install"
export NO_WERROR=1
export BITCOIN_CONFIG="--enable-reduce-exports --enable-experimental-util-chainstate --with-experimental-kernel-lib --enable-shared"
ci: Add environment files for all settings 2019-08-15 16:51:31 -04:00			`#!/usr/bin/env bash`
			`#`
scripted-diff: Bump copyright headers -BEGIN VERIFY SCRIPT- ./contrib/devtools/copyright_header.py update ./ -END VERIFY SCRIPT- Commits of previous years: - 2021: f47dda2c58b5d8d623e0e7ff4e74bc352dfa83d7 - 2020: fa0074e2d82928016a43ca408717154a1c70a4db - 2019: aaaaad6ac95b402fe18d019d67897ced6b316ee0 2022-12-24 23:49:50 +00:00			`# Copyright (c) 2019-2022 The Bitcoin Core developers`
ci: Add environment files for all settings 2019-08-15 16:51:31 -04:00			`# Distributed under the MIT software license, see the accompanying`
			`# file COPYING or http://www.opensource.org/licenses/mit-license.php.`

			`export LC_ALL=C.UTF-8`

ci: Build bitcoin-chainstate ...to make sure that the linker errors that arise from coupling regressions are caught by CI. Adding to the "no wallet" ci job as suggested by MarcoFalke. 2022-02-10 16:08:07 -05:00			`export CONTAINER_NAME=ci_native_nowallet_libbitcoinkernel`
Bump python minimum version to 3.8 Also, switch ci_native_qt5 to g++-9 (from g++-8) to work around bugs. This should be fine, because the i686_centos task still checks for g++-8 compatibility. See https://github.com/bitcoin/bitcoin/pull/27483#issuecomment-1513477050 for the list of bugs. 2023-04-18 14:12:35 +02:00			`export CI_IMAGE_NAME_TAG="ubuntu:20.04"`
build: Bump minimum Clang to clang-10 2023-05-17 10:09:45 +02:00			`# Use minimum supported python3.8 and clang-10, see doc/dependencies.md`
			`export PACKAGES="python3-zmq clang-10 llvm-10 libc++abi-10-dev libc++-10-dev"`
			`export DEP_OPTS="NO_WALLET=1 CC=clang-10 CXX='clang++-10 -stdlib=libc++'"`
ci: Add environment files for all settings 2019-08-15 16:51:31 -04:00			`export GOAL="install"`
ci: avoid using -Werror for older compilers 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. 2023-02-01 11:11:40 +00:00			`export NO_WERROR=1`
build: Bump minimum Clang to clang-10 2023-05-17 10:09:45 +02:00			`export BITCOIN_CONFIG="--enable-reduce-exports --enable-experimental-util-chainstate --with-experimental-kernel-lib --enable-shared"`