libinput/test/helper-copy-and-exec-from-tmp.sh

#!/bin/bash -x
#
# Usage: helper-copy-and-exec-from-tmp.sh /path/to/binary [args]
#
# Copies the given binary into a unique file in /tmp and executes it with
# [args]. Exits with the same return code as the binary did.

executable="$1"
shift

target_name=$(mktemp)
cp "$executable" "$target_name"
chmod +x "$target_name"

"$target_name" "$@"
rc=$?
rm "$target_name"
exit $rc
tools: if the execdir is the builddir, add it to the path When running libinput tools from the builddir, look up the subtools in the builddir as well. Otherwise, add the install prefix to the list of lookup locations. This ensures that a) we're running builddir stuff against builddir stuff, but also b) that we're not running builddir stuff against installed stuff because that may give us false positives. The test was squashed in from a separate patch and was Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> 2018-06-27 13:26:51 +10:00			`#!/bin/bash -x`
			`#`
			`# Usage: helper-copy-and-exec-from-tmp.sh /path/to/binary [args]`
			`#`
			`# Copies the given binary into a unique file in /tmp and executes it with`
			`# [args]. Exits with the same return code as the binary did.`

			`executable="$1"`
			`shift`

			`target_name=$(mktemp)`
			`cp "$executable" "$target_name"`
			`chmod +x "$target_name"`

			`"$target_name" "$@"`
			`rc=$?`
			`rm "$target_name"`
			`exit $rc`