From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: dev@dpdk.org
Cc: Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: [dpdk-dev] [PATCH 0/4] pmdinfogen: support Windows
Date: Sun, 13 Dec 2020 02:34:43 +0300 [thread overview]
Message-ID: <20201212233447.23154-1-dmitry.kozliuk@gmail.com> (raw)
Based on Python version of pmdinfogen, deferred until 21.02:
http://patchwork.dpdk.org/project/dpdk/list/?series=13153
There are a few Python libraries for PE/COFF, none of which suits the need,
so a custom COFF parser is used. Advice is welcome, options considered:
* py-coff (https://github.com/jeppeter/py-coff): doesn't give access to
symbol values, Python 2 code inside, not very popular.
* pefile (https://github.com/erocarrera/pefile): for PE (executables and
libraries), not COFF (objects); most popular.
* pype32-py3 (https://github.com/crackinglandia/pype32): ditto, less popular.
A script to extract object files from library is still required. Meson has
extract_all_objects(), but they can't be passed as inputs to custom_target()
until 0.52.0 (commit f431cff809).
Depends-on: series-13153 ("pmdinfogen: rewrite in Python")
Dmitry Kozlyuk (4):
pmdinfogen: support COFF
pmdinfogen: allow multiple input files
buildtools: support object file extraction for Windows
build: enable pmdinfogen for Windows
buildtools/coff.py | 154 ++++++++++++++++++++++++++++++++
buildtools/gen-pmdinfo-cfile.py | 19 ++++
buildtools/gen-pmdinfo-cfile.sh | 14 ---
buildtools/meson.build | 15 +++-
buildtools/pmdinfogen.py | 126 +++++++++++++++++++-------
drivers/meson.build | 26 +++---
6 files changed, 294 insertions(+), 60 deletions(-)
create mode 100644 buildtools/coff.py
create mode 100644 buildtools/gen-pmdinfo-cfile.py
delete mode 100755 buildtools/gen-pmdinfo-cfile.sh
--
2.29.2
next reply other threads:[~2020-12-12 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 23:34 Dmitry Kozlyuk [this message]
2020-12-12 23:34 ` [dpdk-dev] [PATCH 1/4] pmdinfogen: support COFF Dmitry Kozlyuk
2020-12-12 23:34 ` [dpdk-dev] [PATCH 2/4] pmdinfogen: allow multiple input files Dmitry Kozlyuk
2020-12-12 23:34 ` [dpdk-dev] [PATCH 3/4] buildtools: support object file extraction for Windows Dmitry Kozlyuk
2020-12-12 23:34 ` [dpdk-dev] [PATCH 4/4] build: enable pmdinfogen " Dmitry Kozlyuk
2021-01-08 2:47 ` [dpdk-dev] [PATCH v2 0/4] pmdinfogen: support Windows Dmitry Kozlyuk
2021-01-08 2:47 ` [dpdk-dev] [PATCH v2 1/4] pmdinfogen: support COFF Dmitry Kozlyuk
2021-01-08 2:47 ` [dpdk-dev] [PATCH v2 2/4] pmdinfogen: allow multiple input files Dmitry Kozlyuk
2021-01-08 2:47 ` [dpdk-dev] [PATCH v2 3/4] buildtools: support object file extraction for Windows Dmitry Kozlyuk
2021-01-25 15:57 ` Thomas Monjalon
2021-01-08 2:47 ` [dpdk-dev] [PATCH v2 4/4] build: enable pmdinfogen " Dmitry Kozlyuk
2021-01-08 18:29 ` Jie Zhou
2021-01-25 15:59 ` [dpdk-dev] [PATCH v2 0/4] pmdinfogen: support Windows 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=20201212233447.23154-1-dmitry.kozliuk@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@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).