delta/systemd.git - github.com: systemd/systemd.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	tools: shellcheck-ify tool scripts	Frantisek Sumsal	2021-09-30	1	-2/+3
\|
*	tree-wide: add spdx header on all scripts and helpers	Zbigniew Jędrzejewski-Szmek	2021-01-28	1	-0/+1
\| \| \| \| \| \|	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.
*	meson: use same compilers to build fuzzers	Yu Watanabe	2018-10-09	1	-1/+3
\|
*	meson: check the existence of ninja.build for fuzzer tests	Yu Watanabe	2018-07-23	1	-1/+1
\|
*	oss-fuzz: Fallback to `ninja-build` when available (#8641)	Filipe Brandenburger	2018-04-04	1	-1/+9
\| \| \| \| \|	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.
*	Hook up oss-fuzz test cases as tests	Zbigniew Jędrzejewski-Szmek	2018-01-27	1	-0/+10
	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