From: Brandon Lo <blo@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Windows Mingw-w64 Compilation Testing - Now in Production
Date: Thu, 25 Jun 2020 11:51:54 -0400 [thread overview]
Message-ID: <CAOeXdvbZiK6wO3DCAJQXUr728kZ70MEREJhWa08fmGXB9JN7vA@mail.gmail.com> (raw)
In-Reply-To: <318963625.T9AhtUn35N@thomas>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
Hi Thomas,
Thank you for the update.
I will look out for that fix and enable the flag.
Thanks,
Brandon
On Thu, Jun 25, 2020 at 11:18 AM Thomas Monjalon <thomas@monjalon.net>
wrote:
> 25/06/2020 15:20, Brandon Lo:
> > Hi everyone,
> >
> > We have just started testing patchsets on Windows using Mingw-w64.
> > The test case is labeled as: *dpdk_mingw64_compile*
> >
> > The instructions that are followed can be found here:
> > https://doc.dpdk.org/guides/windows_gsg/build_dpdk.html
> > The VM has installed Mingw-w64 and set the path to include the mingw
> binary
> > files.
> > It runs the meson and ninja commands from part 3.6 in the Windows guide
> to
> > perform compile testing.
> >
> > If there are any issues with the test case and how it is run, feel free
> to
> > let me know.
> > I will also keep my eyes out for any failures.
>
> Good, thank you.
>
> When the patch for thread handle fix will be merged,
> Windows will be able to compile without any warning.
> Then you should test compilation with the meson option --werror please,
> so any warning will be a failure.
>
>
>
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
[-- Attachment #2: Type: text/html, Size: 3165 bytes --]
prev parent reply other threads:[~2020-06-25 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:20 Brandon Lo
2020-06-25 15:18 ` Thomas Monjalon
2020-06-25 15:51 ` Brandon Lo [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=CAOeXdvbZiK6wO3DCAJQXUr728kZ70MEREJhWa08fmGXB9JN7vA@mail.gmail.com \
--to=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--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).