From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: [dpdk-dev] [PATCH] doc: add pmdinfogen rewrite to release notes
Date: Fri, 12 Feb 2021 12:04:31 +0100 [thread overview]
Message-ID: <20210212110431.940131-1-thomas@monjalon.net> (raw)
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
The build tool pmdinfogen was rewritten in DPDK 21.02,
adding Windows support.
There is a new build-time dependency: pyelftools.
Fixes: f0f93a7adfee ("buildtools: use Python pmdinfogen")
Fixes: 6b19edcb663c ("build: enable pmdinfogen for Windows")
Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/rel_notes/release_21_02.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/rel_notes/release_21_02.rst b/doc/guides/rel_notes/release_21_02.rst
index 64e220f2ac..786c70455d 100644
--- a/doc/guides/rel_notes/release_21_02.rst
+++ b/doc/guides/rel_notes/release_21_02.rst
@@ -180,6 +180,13 @@ New Features
tests and output graphed results to PDF files.
See the :doc:`../tools/cryptoperf` guide for more details.
+* **Added Windows support to pmdinfogen.**
+
+ PMD information strings were added for Windows as well as for other OS.
+ Extracting them from Windows DLLs is not yet supported.
+ The build-time tool pmdinfogen was rewritten in Python,
+ thus libelf dependency was replaced with pyelftools as new build dependency.
+
* **Added support for build-time checking of header includes.**
A new build option ``check_includes`` has been added, which, when enabled,
--
2.30.0
next reply other threads:[~2021-02-12 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 11:04 Thomas Monjalon [this message]
2021-02-12 14:17 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2021-02-12 14:29 ` Bruce Richardson
2021-02-12 14:36 ` Kevin Traynor
2021-02-12 15:15 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2021-02-14 9:53 ` 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=20210212110431.940131-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=john.mcnamara@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).