From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: dev@dpdk.org
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Olivier Matz <olivier.matz@6wind.com>,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
Omar Cardona <ocardona@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-dev] [PATCH v3 0/7] MinGW-w64 support
Date: Tue, 18 Feb 2020 03:02:22 +0300 [thread overview]
Message-ID: <20200218000229.86621-1-dmitry.kozliuk@gmail.com> (raw)
This patch series add support for building DPDK using MinGW-w64.
MinGW-w64 provides GNU toolchain and independent platform SDK on
Windows. It also supports cross-compilation to Windows from POSIX
systems by providing cross tollchains and libraries [0]. It does NOT
emulate a full POSIX environment, like Cygwin or MSYS do.
There are advantages in using MinGW-w64 in addition to Clang:
1. Cross-compilation out-of-the-box. MinGW-w64 is provides a pthread
implementation, GNU getopt, and Windows platform SDK.
2. Easier porting of POSIX applications using DPDK to Windows, because
application code can use the same benefits as mentioned above.
3. Having both primary compilers enabled on Windows provides more
diagnostics and generally prevents non-portable code.
[0]: http://mingw-w64.org
v3 Changes:
Rebase onto the latest Windows EAL.
Prevent format attribute conflict with upcoming v20.05 patches.
Remove redundant CFLAGS from Meson.
Remove links to Meson bugtracker from docs (PR merged into upstream).
Fix Clang warnings using about GNU options.
v2 Changes:
Add patch to use lowercase system header filenames.
Move Meson cross-file for x86 to arch directory.
Change wording in comments.
Add Meson version warning in documentation.
---
Dmitry Kozlyuk (7):
eal: introduce portable format attribute
eal/windows: use lowercase filenames for system headers
eal/windows: support builing with MinGW-w64
build: MinGW-w64 support for Meson
build: add cross-file for MinGW-w64
doc: guide for Windows build using MinGW-w64
build: fix linker warnings with Clang on Windows
config/meson.build | 26 +++++++--
config/x86/meson_mingw.txt | 14 +++++
doc/guides/windows_gsg/build_dpdk.rst | 63 ++++++++++++++++++---
lib/librte_cmdline/cmdline.h | 4 +-
lib/librte_eal/common/include/rte_common.h | 17 +++++-
lib/librte_eal/common/include/rte_debug.h | 2 +-
lib/librte_eal/common/include/rte_devargs.h | 2 +-
lib/librte_eal/common/include/rte_log.h | 4 +-
lib/librte_eal/meson.build | 3 +
lib/librte_eal/windows/eal/eal.c | 6 +-
lib/librte_eal/windows/eal/include/getopt.h | 4 ++
lib/librte_eal/windows/eal/include/rte_os.h | 6 +-
lib/meson.build | 8 ++-
13 files changed, 134 insertions(+), 25 deletions(-)
create mode 100644 config/x86/meson_mingw.txt
--
2.25.0
next reply other threads:[~2020-02-18 0:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 0:02 Dmitry Kozlyuk [this message]
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 1/7] eal: introduce portable format attribute Dmitry Kozlyuk
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 2/7] eal/windows: use lowercase filenames for system headers Dmitry Kozlyuk
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 3/7] eal/windows: support builing with MinGW-w64 Dmitry Kozlyuk
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 4/7] build: MinGW-w64 support for Meson Dmitry Kozlyuk
2020-02-18 14:26 ` Thomas Monjalon
2020-02-18 14:54 ` Bruce Richardson
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 5/7] build: add cross-file for MinGW-w64 Dmitry Kozlyuk
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 6/7] doc: guide for Windows build using MinGW-w64 Dmitry Kozlyuk
2020-02-18 21:27 ` William Tu
2020-02-18 0:02 ` [dpdk-dev] [PATCH v3 7/7] build: fix linker warnings with Clang on Windows Dmitry Kozlyuk
2020-02-18 21:16 ` [dpdk-dev] [PATCH v3 0/7] MinGW-w64 support William Tu
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 " Dmitry Kozlyuk
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 1/7] eal: introduce portable format attribute Dmitry Kozlyuk
2020-03-12 22:33 ` Thomas Monjalon
2020-03-13 23:38 ` Dmitry Kozlyuk
2020-03-15 8:36 ` Thomas Monjalon
2020-03-16 10:54 ` Bruce Richardson
2020-03-16 11:02 ` Bruce Richardson
2020-03-16 11:14 ` Thomas Monjalon
2020-03-16 11:18 ` Bruce Richardson
2020-03-16 11:35 ` Bruce Richardson
2020-03-16 14:27 ` Thomas Monjalon
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 2/7] eal/windows: use lowercase filenames for system headers Dmitry Kozlyuk
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 3/7] eal/windows: support builing with MinGW-w64 Dmitry Kozlyuk
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 4/7] build: MinGW-w64 support for Meson Dmitry Kozlyuk
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 5/7] build: add cross-file for MinGW-w64 Dmitry Kozlyuk
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 6/7] doc: guide for Windows build using MinGW-w64 Dmitry Kozlyuk
2020-02-27 4:25 ` [dpdk-dev] [PATCH v4 7/7] build: fix linker warnings with Clang on Windows Dmitry Kozlyuk
2020-03-11 17:22 ` [dpdk-dev] [PATCH v4 0/7] MinGW-w64 support William Tu
2020-03-18 0:24 ` Thomas Monjalon
2020-03-11 22:36 ` Kadam, Pallavi
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=20200218000229.86621-1-dmitry.kozliuk@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=ocardona@microsoft.com \
--cc=olivier.matz@6wind.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@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).