systemd/tools/meson-build.sh

#!/bin/sh
# SPDX-License-Identifier: LGPL-2.1-or-later
set -eux

src="$1"
dst="$2"
target="$3"
options="$4"
CC="$5"
CXX="$6"

# shellcheck disable=SC2086
[ -f "$dst/ninja.build" ] || CC="$CC" CXX="$CXX" meson "$src" "$dst" $options

# Locate ninja binary, on CentOS 7 it is called ninja-build, so
# use that name if available.
ninja="ninja"
if which ninja-build >/dev/null 2>&1 ; then
    ninja="ninja-build"
fi

"$ninja" -C "$dst" "$target"
Hook up oss-fuzz test cases as tests This is a bit painful because a separate build of systemd is necessary. The tests are guarded by tests!=false and slow-tests==true. Running them is not slow, but compilation certainly is. If this proves unwieldy, we can add a separate option controlling those builds later. The build for each sanitizer has its own directory, and we build all fuzzer tests there, and then pull them out one-by-one by linking into the target position as necessary. It would be nicer to just build the desired fuzzer, but we need to build the whole nested build as one unit. [I also tried making systemd and nested meson subproject. This would work nicely, but meson does not allow that because the nested target names are the same as the outer project names. If that is ever fixed, that would be the way to go.] v2: - make sure things still work if memory sanitizer is not available v3: - switch to syntax which works with meson 0.42.1 found in Ubuntu 2018-01-19 17:54:30 +11:00			`#!/bin/sh`
tree-wide: add spdx header on all scripts and helpers Even though many of those scripts are very simple, it is easier to include the header than to try to say whether each of those files is trivial enough not to require one. 2021-01-27 13:37:10 +01:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
Hook up oss-fuzz test cases as tests This is a bit painful because a separate build of systemd is necessary. The tests are guarded by tests!=false and slow-tests==true. Running them is not slow, but compilation certainly is. If this proves unwieldy, we can add a separate option controlling those builds later. The build for each sanitizer has its own directory, and we build all fuzzer tests there, and then pull them out one-by-one by linking into the target position as necessary. It would be nicer to just build the desired fuzzer, but we need to build the whole nested build as one unit. [I also tried making systemd and nested meson subproject. This would work nicely, but meson does not allow that because the nested target names are the same as the outer project names. If that is ever fixed, that would be the way to go.] v2: - make sure things still work if memory sanitizer is not available v3: - switch to syntax which works with meson 0.42.1 found in Ubuntu 2018-01-19 17:54:30 +11:00			`set -eux`

			`src="$1"`
			`dst="$2"`
			`target="$3"`
			`options="$4"`
meson: use same compilers to build fuzzers 2018-10-04 04:52:44 +09:00			`CC="$5"`
			`CXX="$6"`
Hook up oss-fuzz test cases as tests This is a bit painful because a separate build of systemd is necessary. The tests are guarded by tests!=false and slow-tests==true. Running them is not slow, but compilation certainly is. If this proves unwieldy, we can add a separate option controlling those builds later. The build for each sanitizer has its own directory, and we build all fuzzer tests there, and then pull them out one-by-one by linking into the target position as necessary. It would be nicer to just build the desired fuzzer, but we need to build the whole nested build as one unit. [I also tried making systemd and nested meson subproject. This would work nicely, but meson does not allow that because the nested target names are the same as the outer project names. If that is ever fixed, that would be the way to go.] v2: - make sure things still work if memory sanitizer is not available v3: - switch to syntax which works with meson 0.42.1 found in Ubuntu 2018-01-19 17:54:30 +11:00
tools: shellcheck-ify tool scripts 2021-09-29 21:28:55 +02:00			`# shellcheck disable=SC2086`
meson: use same compilers to build fuzzers 2018-10-04 04:52:44 +09:00			`[ -f "$dst/ninja.build" ] \|\| CC="$CC" CXX="$CXX" meson "$src" "$dst" $options`
oss-fuzz: Fallback to `ninja-build` when available (#8641) The ninja binary is deployed as `ninja-build` in older distros such as RHEL 7/CentOS 7. Detect that and use `ninja-build` instead of `ninja` when it's available. 2018-04-04 00:32:59 -07:00
			`# Locate ninja binary, on CentOS 7 it is called ninja-build, so`
			`# use that name if available.`
tools: shellcheck-ify tool scripts 2021-09-29 21:28:55 +02:00			`ninja="ninja"`
oss-fuzz: Fallback to `ninja-build` when available (#8641) The ninja binary is deployed as `ninja-build` in older distros such as RHEL 7/CentOS 7. Detect that and use `ninja-build` instead of `ninja` when it's available. 2018-04-04 00:32:59 -07:00			`if which ninja-build >/dev/null 2>&1 ; then`
tools: shellcheck-ify tool scripts 2021-09-29 21:28:55 +02:00			`ninja="ninja-build"`
oss-fuzz: Fallback to `ninja-build` when available (#8641) The ninja binary is deployed as `ninja-build` in older distros such as RHEL 7/CentOS 7. Detect that and use `ninja-build` instead of `ninja` when it's available. 2018-04-04 00:32:59 -07:00			`fi`

			`"$ninja" -C "$dst" "$target"`