DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tal Shnaiderman <talshn@mellanox.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: "harini.ramakrishnan@microsoft.com"
	<harini.ramakrishnan@microsoft.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] MinGW guide
Date: Mon, 15 Jun 2020 09:25:07 +0000	[thread overview]
Message-ID: <AM0PR05MB53138CD01A5006AB6ECEC8F4A99C0@AM0PR05MB5313.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200615034800.2d9b7590@sovereign>

> Subject: Re: MinGW guide
> 
> On Sat, 13 Jun 2020 10:55:14 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:

[snip]

> > 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.
> 

Where do we actually use pthread in Windows? 

> 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.

I was sure, since we create the threads with Win32 API (CreateThread), the correct option is Win32.
My mingw-w64 is installed with that option and I didn't see issues with it.

> 
> --
> Dmitry Kozlyuk

  reply	other threads:[~2020-06-15  9:25 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
2020-06-15  9:25   ` Tal Shnaiderman [this message]
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=AM0PR05MB53138CD01A5006AB6ECEC8F4A99C0@AM0PR05MB5313.eurprd05.prod.outlook.com \
    --to=talshn@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=harini.ramakrishnan@microsoft.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).