DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	bruce.richardson@intel.com, Rastislav Cernay <cernay@netcope.com>
Cc: dev@dpdk.org, "Jan, Remes" <remes@netcope.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] use pkg-config to find Netcope dependencies
Date: Mon, 16 Sep 2019 16:34:27 +0100	[thread overview]
Message-ID: <d95c4bb1-0a5f-3f40-f402-ae341e18095c@intel.com> (raw)
In-Reply-To: <20190914093700.11451-1-thomas@monjalon.net>

On 9/14/2019 10:36 AM, Thomas Monjalon wrote:
> The libraries required for Netcope PMDs can be found in
> https://www.netcope.com/en/company/community-support/dpdk-libsze2
> 
> These libraries are compatible with pkg-config, which is a better solution
> than directly looking for libraries and includes.
> These patches are using exclusively pkg-config with meson.
> 
> 
> Thomas Monjalon (2):
>   net/nfb: fix dependency check
>   net/szedata2: fix dependency check
> 

+1 to this patch, unrelated to this patch I remember there was an issue with the
nfb & szedata2 dependencies, that their dependencies conflict with each other,
so it wasn't possible to enable both at the same time.

Jan, Rastislav,

Is it still the case, or is there any improvement there?

Thanks,
ferruh

  parent reply	other threads:[~2019-09-16 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14  9:36 Thomas Monjalon
2019-09-14  9:36 ` [dpdk-dev] [PATCH 1/2] net/nfb: fix dependency check Thomas Monjalon
2019-09-15 12:04   ` Jan Remeš
2019-09-16 15:46     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-09-16 15:51       ` Thomas Monjalon
2019-09-14  9:37 ` [dpdk-dev] [PATCH 2/2] net/szedata2: " Thomas Monjalon
2019-09-15 12:05   ` Jan Remeš
2019-09-16 15:34 ` Ferruh Yigit [this message]
2019-09-16 16:52   ` [dpdk-dev] [PATCH 0/2] use pkg-config to find Netcope dependencies Jan Remeš
2019-10-03 15:23 ` Ferruh Yigit

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=d95c4bb1-0a5f-3f40-f402-ae341e18095c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=cernay@netcope.com \
    --cc=dev@dpdk.org \
    --cc=remes@netcope.com \
    --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).