systemd/tools/meson-build.sh

#!/bin/sh
set -eux

src="$1"
dst="$2"
target="$3"
options="$4"

[ -d "$dst" ] || 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 09:54:30 +03:00			`#!/bin/sh`
			`set -eux`

			`src="$1"`
			`dst="$2"`
			`target="$3"`
			`options="$4"`

			`[ -d "$dst" ] \|\| 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 10:32:59 +03:00
			`# 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"`