DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Nick Connolly <nick.connolly@mayadata.io>
Cc: Storage Performance Development Kit <spdk@lists.01.org>,
	Aaron Conole <aconole@redhat.com>, Brandon Lo <blo@iol.unh.edu>,
	 Lincoln Lavoie <lylavoie@iol.unh.edu>,
	"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
	"ci@dpdk.org" <ci@dpdk.org>,  "dev@dpdk.org" <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	 Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	 "Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [dpdk-dev] [SPDK] Re: [dpdklab] Re: [dpdk-ci] [CI] SPDK compilation failures @ DPDK community lab
Date: Mon, 15 Feb 2021 11:15:53 +0100	[thread overview]
Message-ID: <CAJFAV8xf0zKSzXUZ0yP8_3rAgN_QqaFqujjtCurXm8ieAP27ng@mail.gmail.com> (raw)
In-Reply-To: <465398c0-ac79-758f-040b-7152b41c06bd@mayadata.io>

On Mon, Feb 15, 2021 at 10:56 AM Nick Connolly
<nick.connolly@mayadata.io> wrote:
> > Rather than maintain dpdk internal dependencies on SPDK side, would it
> > be possible to use pkg-config?
> Hi David,
>
> Are the DPDK pkgconfig files intended to work for Windows builds?

I cannot find a test linking an example for Windows out of meson.

I don't know what the best solution is for linking an application
against DPDK for Windows.
Cc'd dpdk windows maintainers.


>
> I've had a quick look and as far as I can see the dependencies are
> listed correctly,
> but I was less convinced by the use of -Wl,--whole-archive which is
> specific to the
> GNU linker (Clang/Link configuration requires a sequence of
> -Wl,-wholearchive:<library>).

One of the reasons is to avoid statically linked drivers being dropped
by the linker when no explicit reference exists.


-- 
David Marchand


      reply	other threads:[~2021-02-15 10:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 15:21 [dpdk-dev] " Aaron Conole
2021-02-08 16:03 ` Zawadzki, Tomasz
2021-02-08 16:21   ` [dpdk-dev] [dpdk-ci] " Lincoln Lavoie
     [not found]     ` <DM6PR11MB422097059AB558056B97BEC5EE8F9@DM6PR11MB4220.namprd11.prod.outlook.com>
2021-02-09 15:13       ` Aaron Conole
2021-02-09 16:07         ` [dpdk-dev] [dpdklab] " Brandon Lo
2021-02-09 17:54           ` Brandon Lo
2021-02-11 14:02             ` Aaron Conole
2021-02-11 16:25               ` Brandon Lo
2021-02-12  9:18               ` Zawadzki, Tomasz
2021-02-12 17:39                 ` Brandon Lo
2021-02-15 15:28                   ` Aaron Conole
2021-02-17 16:06                     ` Zawadzki, Tomasz
2021-02-18 13:58                       ` Brandon Lo
2021-02-15  9:12                 ` [dpdk-dev] [SPDK] " David Marchand
2021-02-15  9:56                   ` Nick Connolly
2021-02-15 10:15                     ` David Marchand [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=CAJFAV8xf0zKSzXUZ0yP8_3rAgN_QqaFqujjtCurXm8ieAP27ng@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=blo@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --cc=navasile@linux.microsoft.com \
    --cc=nick.connolly@mayadata.io \
    --cc=pallavi.kadam@intel.com \
    --cc=spdk@lists.01.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).