I wonder if this should be consistent with Nick's meson (to use external
pthread library) change?
-----Original Message-----
From: Dmitry Kozlyuk <dmitry.kozl...@gmail.com>
Sent: Wednesday, December 23, 2020 3:59 AM
To: Tal Shnaiderman <tal...@nvidia.com>
Cc: dev@dpdk.org; thomas <tho...@monjalon.net>; Kadam, Pallavi
<pallavi.ka...@intel.com>; navas...@linux.microsoft.com; Dmitry Malloy
(MESHCHANINOV) <dmit...@microsoft.com>; david.march...@redhat.com
Subject: [EXTERNAL] Re: [PATCH v4] eal: add generic thread-local-storage
functions
On Wed, 23 Dec 2020 11:44:31 +0000, Tal Shnaiderman wrote:
> > > diff --git a/lib/librte_eal/windows/meson.build
> > > b/lib/librte_eal/windows/meson.build
> > > index 3b2faf29eb..1f1398dfe9 100644
> > > --- a/lib/librte_eal/windows/meson.build
> > > +++ b/lib/librte_eal/windows/meson.build
> > > @@ -21,4 +21,10 @@ sources += files(
> > > 'getopt.c',
> > > )
> > >
> > > +if (dpdk_conf.has('use_external_pthread'))
> >
> > Please describe the new option in meson_options.txt.
> > Maybe drop "external" from the name, what do you think?
>
> How about use_windows_pthread to be clear that it's unrelated to UNIX
> pthreads?
Sounds good.
