DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Luca Boccassi <bluca@debian.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] build: document that Meson < 0.46 will fail to list private deps
Date: Fri, 16 Nov 2018 11:47:57 +0000	[thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0726E0F2A@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20181116105733.21200-1-bluca@debian.org>



> -----Original Message-----
> From: Luca Boccassi [mailto:bluca@debian.org]
> Sent: Friday, November 16, 2018 10:58 AM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; thomas@monjalon.net;
> Luca Boccassi <bluca@debian.org>
> Subject: [PATCH v2] build: document that Meson < 0.46 will fail to list
> private deps
> 
> Meson can generate the list of private dependencies of libraries
> automatically for the pkgconfig file only since version 0.46.0.
> 
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> v2: corrected version, minimum required is meson 0.46
> 

Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2018-11-16 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 18:26 [dpdk-dev] [PATCH] build: document that Meson < 0.45 " Luca Boccassi
2018-11-16 10:26 ` Bruce Richardson
2018-11-16 10:52   ` Luca Boccassi
2018-11-16 10:55     ` Luca Boccassi
2018-11-16 10:57 ` [dpdk-dev] [PATCH v2] build: document that Meson < 0.46 " Luca Boccassi
2018-11-16 11:47   ` Richardson, Bruce [this message]
2018-11-18 23:51     ` 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=59AF69C657FD0841A61C55336867B5B0726E0F2A@IRSMSX103.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bluca@debian.org \
    --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).