DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tal Shnaiderman <talshn@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	"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>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Handling missing export functions in MSVC linkage
Date: Sun, 7 Jun 2020 12:26:56 +0000	[thread overview]
Message-ID: <AM0PR05MB53133AE8B0C2C20C5688288FA9840@AM0PR05MB5313.eurprd05.prod.outlook.com> (raw)


I was wondering if there is a known solution for the following problem:

Whenever building a DPDK library using clang/MSVC there is an linkage issue if the rte_*_version.map names a function that isn't being compiled.

For example, in librte_metrics several files in the lib build depend on the existence of jansson, however, since the functions in those files are stated in rte_metrics_version.map MSVC prints out
errors in the linkage stage in case jansson is missing:

*error LNK2001: unresolved external symbol rte_metrics_tel_.... 

In clang build the .map file is converted into Module-Definition (.Def) File.


Is there a way to instruct the linker to ignore missing functions in the def file?



             reply	other threads:[~2020-06-07 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 12:26 Tal Shnaiderman [this message]
2020-06-08  0:09 ` Dmitry Kozlyuk
2020-06-08  8:33   ` David Marchand
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=AM0PR05MB53133AE8B0C2C20C5688288FA9840@AM0PR05MB5313.eurprd05.prod.outlook.com \
    --to=talshn@mellanox.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=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).