From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: harini.ramakrishnan@microsoft.com, talshn@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] MinGW guide
Date: Mon, 15 Jun 2020 03:48:00 +0300 [thread overview]
Message-ID: <20200615034800.2d9b7590@sovereign> (raw)
In-Reply-To: <2439238.EZ8FaLj9Nj@thomas>
On Sat, 13 Jun 2020 10:55:14 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> The Windows user guide is referencing a general link to download MinGW:
> http://mingw-w64.org/doku.php/download
> For those who want to install MinGW on Windows, I thing it is simpler
> to give this more direct link:
> http://mingw-w64.org/doku.php/download/mingw-builds
> It avoids hesitating between different bundles (Cygwin, Msys2, Win-Builds, etc).
Agreed, at least while no package manager is used.
I believe the most direct link would be this one:
https://sourceforge.net/projects/mingw-w64/files/
> Then when installing mingw-w64-install.exe, a choice must be done
> between threads POSIX or Win32.
> If I understand well, POSIX must be chosen?
Yes. DPDK config/meson.build now links with pthread if linker is not link.exe.
Note that maybe this can be relaxed (test needed!), i. e. link with pthread
if it is found, otherwise use shim. Benefit, if this works: no runtime
dependency on "libwinpthread-1.dll" for Windows.
--
Dmitry Kozlyuk
next prev parent reply other threads:[~2020-06-15 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 8:55 Thomas Monjalon
2020-06-15 0:48 ` Dmitry Kozlyuk [this message]
2020-06-15 9:25 ` Tal Shnaiderman
2020-06-16 21:34 ` Dmitry Kozlyuk
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=20200615034800.2d9b7590@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=talshn@mellanox.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).