ff12a7954c
As in2a5fcfae02and in3e67e5c992using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability.
23 lines
349 B
Bash
Executable file
23 lines
349 B
Bash
Executable file
#!/usr/bin/env bash
|
|
set -e
|
|
|
|
cflags=CFLAGS="$CFLAGS"
|
|
cxxflags=CXXFLAGS="$CXXFLAGS"
|
|
declare -a args
|
|
j=0
|
|
for i in "$@"; do
|
|
case "$i" in
|
|
CFLAGS=*)
|
|
cflags="$i";;
|
|
CXXFLAGS=*)
|
|
cxxflags="$i";;
|
|
*)
|
|
args[$j]="$i"
|
|
j=$((j+1))
|
|
esac
|
|
done
|
|
|
|
export "$cflags" "$cxxflags"
|
|
set -x
|
|
exec meson build "${args[@]}"
|