From: Thomas Monjalon <thomas@monjalon.net>
To: Tal Shnaiderman <talshn@nvidia.com>
Cc: Nick Connolly <nick.connolly@mayadata.io>,
dev@dpdk.org,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
"Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2] windows: minor build fixes
Date: Fri, 13 Nov 2020 15:02:51 +0100 [thread overview]
Message-ID: <3636220.pJOGQ9ufTJ@thomas> (raw)
In-Reply-To: <CY4PR1201MB2548FF751C4D20E31B648088A4E70@CY4PR1201MB2548.namprd12.prod.outlook.com>
12/11/2020 22:35, Tal Shnaiderman:
> > Subject: Re: [dpdk-dev] [PATCH v2] windows: minor build fixes
> >
> > Missing / incorrect '--in-reply-to'. Please ignore - still learning the process!
> >
> > On 31/10/2020 06:43, Nick Connolly wrote:
> > > Meson versions >= 0.54.0 include support for handling /implib with
> > > msvc link. Specifying it explicitly causes failures when linking
> > > against the dll. Tested using Link 14.27.29112.0 and Clang 11.0.0.
> > >
>
> How can we verify this behavior change in 0.54 is intentional?
> I cannot find it in the versions' release notes:
>
> https://mesonbuild.com/Release-notes-for-0-54-0.html
I've found 2 commits touching implib in meson 0.54:
https://github.com/mesonbuild/meson/commit/cace70c64eab4
https://github.com/mesonbuild/meson/commit/06bbf6cf9353f6
next prev parent reply other threads:[~2020-11-13 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 6:39 [dpdk-dev] [PATCH v2] windows: minor build fixes Nick Connolly
2020-10-31 6:43 ` Nick Connolly
2020-10-31 7:00 ` Nick Connolly
2020-11-12 21:35 ` Tal Shnaiderman
2020-11-13 14:02 ` Thomas Monjalon [this message]
2020-11-15 11:20 ` Tal Shnaiderman
-- strict thread matches above, loose matches on Subject: below --
2020-10-30 17:46 [dpdk-dev] [PATCH] Windows: " Nick Connolly
2020-10-31 6:44 ` [dpdk-dev] [PATCH v2] windows: " Nick Connolly
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=3636220.pJOGQ9ufTJ@thomas \
--to=thomas@monjalon.net \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=nick.connolly@mayadata.io \
--cc=ranjit.menon@intel.com \
--cc=talshn@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.