The user cannot override the setup command options --cross-file and
--native-file because the meson-wrapper places these options on the
command line after the user options. This problem was noticed when
trying to build with an SDK using a custom cross-file.
Signed-off-by: Tom Hochstein <tom.hochstein@oss.nxp.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
unset CC CXX CPP LD AR NM STRIP
case "$1" in
-setup|configure|dist|install|introspect|init|test|wrap|subprojects|rewrite|compile|devenv|env2mfile|help) MESON_CMD="$1" ;;
-*) echo meson-wrapper: Implicit setup command assumed; MESON_CMD=setup ;;
+setup|configure|dist|install|introspect|init|test|wrap|subprojects|rewrite|compile|devenv|env2mfile|help)
+ MESON_CMD="$1"
+ shift
+ ;;
+*)
+ MESON_CMD=setup
+ echo meson-wrapper: Implicit setup command assumed
+ ;;
esac
if [ "$MESON_CMD" = "setup" ]; then
fi
exec "$OECORE_NATIVE_SYSROOT/usr/bin/meson.real" \
- "$@" \
- $MESON_SETUP_OPTS
+ $MESON_CMD \
+ $MESON_SETUP_OPTS \
+ "$@"