From: Anand Rawat <anand.rawat@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Cc: Ranjit Menon <ranjit.menon@intel.com>
Subject: Re: [dpdk-dev] [PATCH] build: automatically create windows exports file
Date: Fri, 12 Apr 2019 15:56:13 -0700 [thread overview]
Message-ID: <a8b7171b-71a7-5533-d6c6-158e0768f68b@intel.com> (raw)
Message-ID: <20190412225613.4UFyfl5Ha_LuyGnj6wChKdzYtENnVmwbi3ppep4sUMA@z> (raw)
In-Reply-To: <20190412082900.41784-1-bruce.richardson@intel.com>
On 4/12/2019 1:29 AM, Bruce Richardson wrote:
> Rather than having a separate version.map file for linux/BSD and an
> exports definition file for windows for each library, generate the
> latter from the former automatically at build time.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>
Acked-by: Anand Rawat <anand.rawat@intel.com>
--
Anand Rawat
next prev parent reply other threads:[~2019-04-12 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 8:29 Bruce Richardson
2019-04-12 8:29 ` Bruce Richardson
2019-04-12 22:56 ` Anand Rawat [this message]
2019-04-12 22:56 ` Anand Rawat
2019-04-17 16:21 ` Thomas Monjalon
2019-04-17 16:21 ` Thomas Monjalon
2019-05-29 14:46 ` Bruce Richardson
2019-06-05 17:04 ` Thomas Monjalon
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=a8b7171b-71a7-5533-d6c6-158e0768f68b@intel.com \
--to=anand.rawat@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ranjit.menon@intel.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
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).