From: Tal Shnaiderman <talshn@nvidia.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <pallavi.kadam@intel.com>,
<dmitry.kozliuk@gmail.com>, <navasile@linux.microsoft.com>,
<dmitrym@microsoft.com>, <gakhil@marvell.com>,
<declan.doherty@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] security: build on Windows
Date: Wed, 15 Sep 2021 19:26:03 +0300 [thread overview]
Message-ID: <20210915162603.16652-2-talshn@nvidia.com> (raw)
In-Reply-To: <20210915162603.16652-1-talshn@nvidia.com>
Build the security library on Windows.
Remove unneeded export from version file.
Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
---
Depends-on: patch-98796 ("cryptodev: build on Windows")
---
lib/meson.build | 1 +
lib/security/version.map | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/meson.build b/lib/meson.build
index 5f3b1cf365..e5f0094a82 100644
--- a/lib/meson.build
+++ b/lib/meson.build
@@ -86,6 +86,7 @@ if is_windows
'gso',
'latencystats',
'pdump',
+ 'security',
] # only supported libraries for windows
endif
diff --git a/lib/security/version.map b/lib/security/version.map
index c44c7f5f60..6067051552 100644
--- a/lib/security/version.map
+++ b/lib/security/version.map
@@ -1,7 +1,6 @@
DPDK_22 {
global:
- rte_security_attach_session;
rte_security_capabilities_get;
rte_security_capability_get;
rte_security_session_create;
--
2.16.1.windows.4
next prev parent reply other threads:[~2021-09-15 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 16:26 [dpdk-dev] [PATCH 1/2] security: use the net library for IP structs Tal Shnaiderman
2021-09-15 16:26 ` Tal Shnaiderman [this message]
2021-09-19 14:07 ` [dpdk-dev] [PATCH 2/2] security: build on Windows William Tu
2021-09-29 19:55 ` Kadam, Pallavi
2021-09-30 6:33 ` Tal Shnaiderman
2021-10-01 13:44 ` William Tu
2021-09-15 18:28 ` [dpdk-dev] [EXT] [PATCH 1/2] security: use the net library for IP structs Akhil Goyal
2021-09-16 18:40 ` Tal Shnaiderman
2021-09-19 14:06 ` [dpdk-dev] " William Tu
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=20210915162603.16652-2-talshn@nvidia.com \
--to=talshn@nvidia.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=gakhil@marvell.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--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).