From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] build: get version number from header file
Date: Fri, 31 Aug 2018 15:10:42 +0100 [thread overview]
Message-ID: <1535724642.11823.26.camel@debian.org> (raw)
In-Reply-To: <20180831135132.14730-1-thomas@monjalon.net>
On Fri, 2018-08-31 at 15:51 +0200, Thomas Monjalon wrote:
> The header file rte_version.h should be the unique place
> to define the version number.
> The makefile command "showversion" makes it accessible,
> and it is used to set the meson project version with an external
> command.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>
> I don't know how to check easily the meson version number.
> Please help in testing, thanks.
>
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 84af32ece..b9d1030e7 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -2,7 +2,7 @@
> # Copyright(c) 2017 Intel Corporation
>
> project('DPDK', 'C',
> - version: '18.11-rc0',
> + version: run_command('make',
> 'showversion').stdout().strip(),
> license: 'BSD',
> default_options: ['buildtype=release',
> 'default_library=static'],
> meson_version: '>= 0.41'
Isn't the ultimate end goal to remove the makefiles? If so, shouldn't
meson be independent?
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-08-31 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 13:51 Thomas Monjalon
2018-08-31 14:10 ` Luca Boccassi [this message]
2018-08-31 14:24 ` Bruce Richardson
2018-08-31 16:26 ` Thomas Monjalon
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=1535724642.11823.26.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).