DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Tal Shnaiderman <talshn@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 "ranjit.menon@intel.com" <ranjit.menon@intel.com>,
	 "pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
	 Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
	 "navasile@linux.microsoft.com" <navasile@linux.microsoft.com>,
	 "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	William Tu <u9012063@gmail.com>,
	 "Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>,
	Fady Bader <fady@mellanox.com>,
	 Tasnim Bashar <tbashar@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Handling missing export functions in MSVC linkage
Date: Mon, 8 Jun 2020 10:33:39 +0200	[thread overview]
Message-ID: <CAJFAV8xGRVQBKFXPz58YmZe1Q-=y3U0h2ga9sAmJYVqyU3PJQw@mail.gmail.com> (raw)
In-Reply-To: <20200608030932.5d09c061@sovereign>

On Mon, Jun 8, 2020 at 2:09 AM Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
> On Sun, 7 Jun 2020 12:26:56 +0000
> Tal Shnaiderman <talshn@mellanox.com> wrote:
> > In clang build the .map file is converted into Module-Definition (.Def) File.
> If you create a .def manually, it will override the generation from .map. Of
> cause, this adds manual work and ideally all .def files should be generated.

On this topic, I just noticed that a patch of mine, that removed
rte_eal_get_configuration() from the stable ABI, missed the
declaration in rte_eal_exports.def.
Probably worth adding a check in devtools/, to avoid further misalignment.

David Marchand

  reply	other threads:[~2020-06-08  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 12:26 Tal Shnaiderman
2020-06-08  0:09 ` Dmitry Kozlyuk
2020-06-08  8:33   ` David Marchand [this message]
2021-03-26  8:39     ` Thomas Monjalon
2021-03-26 14:14       ` [dpdk-dev] [EXTERNAL] " Tyler Retzlaff
2020-06-08 15:06   ` [dpdk-dev] " Tal Shnaiderman

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJFAV8xGRVQBKFXPz58YmZe1Q-=y3U0h2ga9sAmJYVqyU3PJQw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=Harini.Ramakrishnan@microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=fady@mellanox.com \
    --cc=navasile@linux.microsoft.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=talshn@mellanox.com \
    --cc=tbashar@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=u9012063@gmail.com \


* 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).