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:focal
# Use minimum supported python3.7 (or python3.8, as best-effort) and clang-8, see doc/dependencies.md
export PACKAGES="python3-zmq clang-8 llvm-8 libc++abi-8-dev libc++-8-dev"
export DEP_OPTS="NO_WALLET=1 CC=clang-8 CXX='clang++-8 -stdlib=libc++'"
export GOAL="install"
export NO_WERROR=1
export BITCOIN_CONFIG="--enable-reduce-exports CC=clang-8 CXX='clang++-8 -stdlib=libc++' --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 20:49:50 -03: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 18:08:07 -03:00			`export CONTAINER_NAME=ci_native_nowallet_libbitcoinkernel`
ci: Bump nowallet_libbitcoinkernel task to ubuntu:focal This is needed to work around https://github.com/bitcoin/bitcoin/pull/27340#issuecomment-1484988445 The only change should be that python3.7 is bumped to 3.8, but this is fine because ci/test/00_setup_env_native_qt5.sh still checks for python3.7 compatibility. 2023-03-29 10:51:03 -03:00			`export CI_IMAGE_NAME_TAG=ubuntu:focal`
			`# Use minimum supported python3.7 (or python3.8, as best-effort) and clang-8, see doc/dependencies.md`
			`export PACKAGES="python3-zmq clang-8 llvm-8 libc++abi-8-dev libc++-8-dev"`
ci/doc: Set minimum required clang/libc++ version to 8.0 2022-01-26 05:30:25 -03:00			`export DEP_OPTS="NO_WALLET=1 CC=clang-8 CXX='clang++-8 -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 08:11:40 -03:00			`export NO_WERROR=1`
ci: Build libbitcoinkernel 2022-02-10 18:08:07 -03:00			`export BITCOIN_CONFIG="--enable-reduce-exports CC=clang-8 CXX='clang++-8 -stdlib=libc++' --enable-experimental-util-chainstate --with-experimental-kernel-lib --enable-shared"`