From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] buildtools: allow a different minimum meson version for Windows
Date: Wed, 18 Jun 2025 11:51:29 +0200 [thread overview]
Message-ID: <CAJFAV8znce+o2Qcu9tqHzgZ8JyojqjQ4vu+BqpK03fa_KwUB9w@mail.gmail.com> (raw)
In-Reply-To: <aFA6e5m-4I4vpSna@bricha3-mobl1.ger.corp.intel.com>
On Mon, Jun 16, 2025 at 5:38 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> On Mon, Jun 16, 2025 at 08:31:11AM -0700, Andre Muezerie wrote:
> > There is a minimum meson version specified in the DPDK meson project
> > section, which has been documented. This string is parsed by
> > buildtools\get-min-meson-version.py and this information is used by
> > lab automation to install the corresponding meson package on the
> > build machine.
> >
> > Turns out that the meson version specified on the DPDK project
> > (0.57.x) is buggy on Windows: it has issues related to path
> > manipulation, and these issues are causing failures. Therefore,
> > a newer meson is required on Windows.
> >
> > To avoid bringing the minimum requirements up for all operating
> > systems before a more appropriate release, this patch implements
> > a mechanism allowing a different version to be specified for Windows.
> >
> > Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
Two (non blocking) comments on this patch:
- could you send a followup patch for using this with the MSVC target
in GHA (see .github/workflows/build.yml) ?
- there is nothing really checking whether the minimum version is
correct on Windows.
Would it make sense to have a "runtime" check in meson out of the
project() declaration?
Something like (untested, probably broken):
diff --git a/meson.build b/meson.build
index 2423884df7..22128b6942 100644
--- a/meson.build
+++ b/meson.build
@@ -11,9 +11,13 @@ project('DPDK', 'c',
'warning_level=2',
],
meson_version: '>= 0.57.2'
- # meson_version_windows: '>= 1.5.2'
)
+meson_version_windows='1.5.2'
+if is_windows and meson.version() < meson_version_windows
+ error('Minimum meson version on Windows is ' + meson_version_windows)
+endif
+
fs = import('fs')
# check for developer mode
--
David Marchand
prev parent reply other threads:[~2025-06-18 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 16:14 [PATCH] " Andre Muezerie
2025-06-16 7:36 ` Bruce Richardson
2025-06-16 8:27 ` Bruce Richardson
2025-06-16 15:09 ` Andre Muezerie
2025-06-16 15:16 ` Bruce Richardson
2025-06-16 15:31 ` [PATCH v2] " Andre Muezerie
2025-06-16 15:38 ` Bruce Richardson
2025-06-18 9:51 ` David Marchand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJFAV8znce+o2Qcu9tqHzgZ8JyojqjQ4vu+BqpK03fa_KwUB9w@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=andremue@linux.microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).