From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, <techboard@dpdk.org>
Subject: RE: Meson get_cross_property deprecated
Date: Fri, 20 Sep 2024 11:20:12 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F707@smartserver.smartshare.dk> (raw)
In-Reply-To: <Zu07aBDU2nB1JPZ6@bricha3-mobl1.ger.corp.intel.com>
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Friday, 20 September 2024 11.08
>
> On Fri, Sep 20, 2024 at 10:22:59AM +0200, Morten Brørup wrote:
> > Hi Bruce,
> >
> >
> > Meson version 1.3.2 emits a notice that meson.get_cross_property is
> > deprecated:
> >
> >
> > NOTICE: Future-deprecated features used:
> >
> > * 0.58.0: {'meson.get_cross_property'}
> >
> >
> > It seems to have been replaced by meson.get_external_property:
> >
> > [1]https://mesonbuild.com/Reference-manual_builtin_meson.html#mesonget_
> > cross_property
> >
> >
> Unfortunately, according to the docs, get_external_property is only
> supported from 0.54 onwards, so we can't update to use it until we do a
> meson minimum-version bump.
>
> Cc: techboard
> Question for community & techboard: is it better to bump minimum version
> now in 24.11, or to wait till after the LTS release? Thoughts?
>
> /Bruce
I think we should bump the minimum Meson version now, or we will be stuck with it for the lifetime of the LTS release.
Also applies to minimum Python version, discussed in another thread:
https://inbox.dpdk.org/dev/ZuwfsT6iRqcjnxRe@bricha3-mobl1.ger.corp.intel.com/
-Morten
prev parent reply other threads:[~2024-09-20 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 8:22 Morten Brørup
2024-09-20 9:07 ` Bruce Richardson
2024-09-20 9:20 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35E9F707@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@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).