: relative-path-resolution
:
: resolve_dylib_path must join a relative path with this executable's
: own directory and normalize it, the contract an installed,
: config.install.relocatable=true consumer relies on (see
: ../direct-driver-loading and libmoltenvk/PACKAGE-README.md's
: "Direct driver loading mode"). Stage a marker file at the expected
: relative location, relative to $exe_dir (this test's own build
: output directory, where the executable itself also lives), matching
: where an installed consumer would place a relocated dylib. Outside
: the script's own working directory, so cleaned up manually rather
: than via a cleanup registration.
:
mkdir -p $exe_dir/../fixture;
touch $exe_dir/../fixture/marker;
$* ../fixture/marker;
^rm -r $exe_dir/../fixture
