From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
"'Jason Messer'" <jmesser@microsoft.com>,
"'Harini Ramakrishnan'" <harini.ramakrishnan@microsoft.com>,
"'Omar Cardona'" <ocardona@microsoft.com>,
"'Ranjit Menon'" <ranjit.menon@intel.com>,
"'Mattias Rönnblom'" <mattias.ronnblom@ericsson.com>,
"'Jeff Shaw'" <jeffrey.b.shaw@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] Compiler for Windows
Date: Tue, 8 Jan 2019 10:24:25 +0000 [thread overview]
Message-ID: <0922dbbe-4d58-3bbb-b84e-1df70d504b76@intel.com> (raw)
In-Reply-To: <24170945.hIekyy4cRm@xps>
On 07-Jan-19 5:08 PM, Thomas Monjalon wrote:
> 07/01/2019 18:00, Bruce Richardson:
>> I think for windows we probably want to start with the MS compiler first,
>> since from my understanding it's probably the default go-to compiler for
>> developers on windows, and look at alternatives from there.
>
> Not sure. I feel clang is a better option.
> This is the purpose of this thread: which compiler can work
> with the DPDK code base? Which modifications of code are acceptable?
>
> Unfortunately we lost my original attempt of getting some facts.
>
i'm developing on a Windows machine, and use clang as code analyzer. so
while the compiling and linking may take some effort, the bulk of it
appears to be working without too much complaints from clang. it's easy
to install as well - just install LLVM and you're good to go.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-01-08 10:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 22:45 Thomas Monjalon
2019-01-03 6:33 ` Stephen Hemminger
2019-01-03 17:10 ` Jason Messer
2019-01-03 17:32 ` Thomas Monjalon
2019-01-03 22:46 ` Wiles, Keith
2019-01-07 10:56 ` Burakov, Anatoly
2019-01-07 15:51 ` Stephen Hemminger
2019-01-07 16:15 ` Bruce Richardson
2019-01-07 16:29 ` Burakov, Anatoly
2019-01-07 16:51 ` Stephen Hemminger
2019-01-07 17:00 ` Bruce Richardson
2019-01-07 17:08 ` Thomas Monjalon
2019-01-08 10:24 ` Burakov, Anatoly [this message]
2019-01-30 14:21 ` Thomas Monjalon
2019-01-30 16:32 ` Menon, Ranjit
2019-01-31 17:12 ` Wiles, Keith
2019-01-31 17:36 ` Thomas Monjalon
2019-01-31 17:48 ` Wiles, Keith
2019-02-13 16:11 ` Thomas Monjalon
2019-02-13 16:35 ` Menon, Ranjit
2019-01-08 12:51 ` Morten Brørup
2019-01-08 14:10 ` Mattias Rönnblom
2019-01-07 17:00 ` Thomas Monjalon
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=0922dbbe-4d58-3bbb-b84e-1df70d504b76@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=jeffrey.b.shaw@intel.com \
--cc=jmesser@microsoft.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=ocardona@microsoft.com \
--cc=ranjit.menon@intel.com \
--cc=stephen@networkplumber.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).