DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Tal Shnaiderman <talshn@mellanox.com>
Cc: 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 03:09:32 +0300
Message-ID: <20200608030932.5d09c061@sovereign> (raw)
In-Reply-To: <AM0PR05MB53133AE8B0C2C20C5688288FA9840@AM0PR05MB5313.eurprd05.prod.outlook.com>

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.


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

There is /FORCE:UNRESOLVED, but it will ignore *any* unresolved reference,
that's why I'm against using it---this can lead to hard-to-diagnose errors.

https://docs.microsoft.com/en-us/cpp/build/reference/force-force-file-output?view=vs-2019

The only proper way I see is forgenertor script to analyze both names .map and
symbols .lib to filter out undefined functions. Dumpbin.exe should be able to
list symbols and it comes with MS Windows SDK, IIRC.

-- 
Dmitry Kozlyuk

  reply	other threads:[~2020-06-08  0:09 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 [this message]
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:
  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=20200608030932.5d09c061@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=Harini.Ramakrishnan@microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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 \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git