From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Bruce Richardson" <bruce.richardson@intel.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jason Messer <jmesser@microsoft.com>,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
Omar Cardona <ocardona@microsoft.com>,
Ranjit Menon <ranjit.menon@intel.com>,
Jeff Shaw <jeffrey.b.shaw@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] Compiler for Windows
Date: Tue, 8 Jan 2019 15:10:37 +0100 [thread overview]
Message-ID: <a5c3c95f-f028-c2d8-dc95-93960d7360ad@ericsson.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35B425AE@smartserver.smartshare.dk>
On 2019-01-08 13:51, Morten Brørup wrote:
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of 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.
>>
>> /Bruce
>
> Having developed quite a bit in Windows myself (about a decade ago), I tend to agree with Bruce here. However, I would add that it depends on who we are targeting:
>
> If we are targeting typical Windows developers (of all levels of experience), it's my impression that Microsoft's compiler IDE, Visual Studio (or Visual Studio Code), is their tool of choice, and anything else would introduce a learning curve. (This is probably more true for junior developers than senior developers, who often have worked in a range of different development environments.)
>
Visual Studio supports clang, and regardless, maximizing the
*convenience* for a few Windows developers shouldn't really be a
priority. Let's be real; Windows is very likely to remain a minor player
in the domain of operating systems for network processing.
Just to be clear, I'm not saying we should sabotage a Windows port. What
I am voting against, is to allow a Windows port to sabotage the DPDK
source code, and prevent the use of useful compiler features, messing up
the code in the process.
As for junior developers, if they are going to program in DPDK,
installing a compiler is such a minor part of the learning curve ahead,
they won't notice the tiny bit of extra climb.
> If we are targeting developers who want to make their applications compatible across multiple operating systems, any compiler would probably work just fine - and in this case, the real question is about making the "make" environment as cross-platform compatible as possible.
>
The discussion has been about compilers, not any build system or tools.
> Maybe you can get inspiration by looking at other cross-platform projects... Google Chrome, Mozilla Firefox, Wireshark, etc.
>
As mentioned in this thread already, Chromium relies on clang.
next prev parent reply other threads:[~2019-01-08 14:10 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
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 [this message]
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=a5c3c95f-f028-c2d8-dc95-93960d7360ad@ericsson.com \
--to=mattias.ronnblom@ericsson.com \
--cc=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=mb@smartsharesystems.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).