DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: John Alexander <John.Alexander@datapath.co.uk>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Meson Minimum Version
Date: Fri, 9 Oct 2020 16:59:42 +0100	[thread overview]
Message-ID: <20201009155942.GE1474@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <DB6PR0902MB20727953CCA842ADCA5B464AB4390@DB6PR0902MB2072.eurprd09.prod.outlook.com>

On Thu, Sep 24, 2020 at 02:22:03PM +0000, John Alexander wrote:
> Hi,
> 
> I've submitted a patch that uses new features of Meson, specifically the directory patch aspect of the subproject feature.  This requires a minimum Meson version of 0.55.0.  How do we go about getting the community to accept a more recent version of Meson and getting the Travis server upgraded too so the CI builds succeed?
> 
> Patch link for reference: http://patches.dpdk.org/patch/78675/
> 
> Kind Regards,
> John Alexander.

Hi John,

this meson version change came up for discussion at the last DPDK technical
board meeting, and some concerns were expressed about the jump in version
and how it might impact those trying to package DPDK.

However, looking at your proposed patch, I wonder though if we really need
to globally bump the meson version, and whether we can limit the
requirements to just windows builds - which is what your patch targets.
Would the following change to your patch work for you? It keeps the minimum
meson version at 0.47.1 but then later does a windows-specific version
check, printing out an error message if requirements not met?

/Bruce

$ git diff
diff --git a/config/meson.build b/config/meson.build
index 69f2aeb60..fd48c9828 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -14,6 +14,11 @@ foreach env:supported_exec_envs
        set_variable('is_' + env, exec_env == env)
 endforeach

+# for windows, we need meson 0.55
+if is_windows and meson.version().version_compare('< 0.55')
+       error('Require meson 0.55 to build on windows')
+endif
+
 # MS linker requires special treatment.
 # TODO: use cc.get_linker_id() with Meson >= 0.54
 is_ms_linker = is_windows and (cc.get_id() == 'clang')
diff --git a/meson.build b/meson.build
index 9e061c73b..7dba3264e 100644
--- a/meson.build
+++ b/meson.build
@@ -8,7 +8,7 @@ project('DPDK', 'C',
                files('VERSION')).stdout().strip(),
        license: 'BSD',
        default_options: ['buildtype=release', 'default_library=static'],
-       meson_version: '>= 0.55.0'
+       meson_version: '>= 0.47.1'
 )

 # set up some global vars for compiler, platform, configuration, etc.



  parent reply	other threads:[~2020-10-09 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 14:22 John Alexander
2020-09-24 14:38 ` Bruce Richardson
2020-10-09 15:59 ` Bruce Richardson [this message]
2020-10-09 16:15   ` John Alexander
2020-09-24 15:32 John Alexander
2020-09-24 15:43 ` Bruce Richardson
2020-09-25  7:31   ` Morten Brørup
2020-09-25  8:41     ` Bruce Richardson
2020-09-25  8:58       ` Morten Brørup
2020-09-25  9:19       ` Dmitry Kozlyuk
2020-09-25  9:22         ` Bruce Richardson

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=20201009155942.GE1474@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=John.Alexander@datapath.co.uk \
    --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).