From: Erik Skultety <eskultet@redhat.com>
Date: Wed, 25 Jan 2023 12:22:49 +0000 (+0100)
Subject: ci: build.sh: Use 'meson setup' explicitly
X-Git-Tag: v9.7.0-rc1~140
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b845c2fd3b820d95a43d8e7c05083dd3852056f4;p=thirdparty%2Flibvirt.git

ci: build.sh: Use 'meson setup' explicitly

Even though 'setup' is assumed when no other command is given, we're
being explicit in our GitLab recipes, so do the same for the local
build.sh script too.

Signed-off-by: Erik Skultety <eskultet@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
---

diff --git a/ci/build.sh b/ci/build.sh
index 3fa28eafa8..c7cba6ffa8 100644
--- a/ci/build.sh
+++ b/ci/build.sh
@@ -8,7 +8,7 @@ export VIR_TEST_DEBUG=1
 # populated at build time from the Dockerfile. A typical use case would
 # be to pass options to trigger cross-compilation
 
-meson build --werror $MESON_OPTS $CI_MESON_ARGS || \
+meson setup build --werror $MESON_OPTS $CI_MESON_ARGS || \
 (cat build/meson-logs/meson-log.txt && exit 1)
 
 ninja -C build $CI_NINJA_ARGS