DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, "Kadam, Pallavi" <pallavi.kadam@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] improve MinGW-w64 support
Date: Tue, 23 Jun 2020 16:44:08 +0200	[thread overview]
Message-ID: <7617588.MaIbcVU7qc@thomas> (raw)
In-Reply-To: <c6ea2505-ce36-a9b5-c2a8-2e7c316dd67a@intel.com>

22/06/2020 22:51, Kadam, Pallavi:
> On 6/20/2020 3:35 PM, Dmitry Kozlyuk wrote:
> > Following the discussion on the mailing list [1], clarify MinGW-w64
> > installation process and stop linking with pthread on Windows.
> > Make Meson cross-file more general along the way.
> > 
> > [1]: https://mails.dpdk.org/archives/dev/2020-June/170252.html
> > 
> > Dmitry Kozlyuk (3):
> >    config: never link with pthread on Windows
> >    config/x86: don't use absolute paths for MinGW-w64 cross toolchain
> >    doc/windows: clarify installation for MinGW-w64
> > 
> >   config/meson.build                    |  2 +-
> >   config/x86/meson_mingw.txt            | 12 ++++++------
> >   doc/guides/windows_gsg/build_dpdk.rst | 12 +++++++-----
> >   doc/guides/windows_gsg/run_apps.rst   |  7 +------
> >   4 files changed, 15 insertions(+), 18 deletions(-)
> > 
> Nice to have a direct link to install MinGW on Windows.
> 
> Acked-by: Pallavi Kadam <pallavi.kadam@intel.com>

Applied, thanks




      reply	other threads:[~2020-06-23 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 22:35 Dmitry Kozlyuk
2020-06-20 22:35 ` [dpdk-dev] [PATCH 1/3] config: never link with pthread on Windows Dmitry Kozlyuk
2020-06-20 22:35 ` [dpdk-dev] [PATCH 2/3] config/x86: don't use absolute paths for MinGW-w64 cross toolchain Dmitry Kozlyuk
2020-06-20 22:35 ` [dpdk-dev] [PATCH 3/3] doc/windows: clarify installation for MinGW-w64 Dmitry Kozlyuk
2020-06-22 20:51 ` [dpdk-dev] [PATCH 0/3] improve MinGW-w64 support Kadam, Pallavi
2020-06-23 14:44   ` Thomas Monjalon [this message]

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=7617588.MaIbcVU7qc@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.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).