From: Bruce Richardson <bruce.richardson@intel.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2] buildtools: allow a different minimum meson version for Windows
Date: Mon, 16 Jun 2025 16:38:35 +0100 [thread overview]
Message-ID: <aFA6e5m-4I4vpSna@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1750087871-27179-1-git-send-email-andremue@linux.microsoft.com>
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>
> ---
> buildtools/get-min-meson-version.py | 8 ++++++--
> meson.build | 1 +
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
Seems a reasonable, simple workaround to me.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
prev parent reply other threads:[~2025-06-16 15:38 UTC|newest]
Thread overview: 7+ 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 [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=aFA6e5m-4I4vpSna@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=andremue@linux.microsoft.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).