From: Stephen Hemminger <stephen@networkplumber.org>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "Bruce Richardson" <bruce.richardson@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>,
"'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: Mon, 7 Jan 2019 08:51:25 -0800 [thread overview]
Message-ID: <20190107085125.3e3adf05@hermes.lan> (raw)
In-Reply-To: <4ca4ff83-d226-12c4-913c-22737dfc5bb6@intel.com>
On Mon, 7 Jan 2019 16:29:25 +0000
"Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:
> On 07-Jan-19 4:15 PM, Bruce Richardson wrote:
> > On Mon, Jan 07, 2019 at 07:51:38AM -0800, Stephen Hemminger wrote:
> >> On Mon, 7 Jan 2019 10:56:57 +0000
> >> "Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:
> >>
> >>> On 03-Jan-19 6:33 AM, Stephen Hemminger wrote:
> >>>> What about Gcc under the WSL thing (ie Linux emulation in Windows).
> >>>> Much better than Cygwin type stuff.
> >>>>
> >>>
> >>> WSL is dog-slow with any kind of disk I/O, at least currently, so while
> >>> i do use WSL to fool my IDE into thinking it's running on Linux, the
> >>> actual compilation user experience is horrible.
> >>>
> >>
> >> The newest version uses Hyper-V to run Linux kernel in VM and is better.
> >> Probably all still has issues with translation to NTFS.
>
> Yes, but it takes a while for "newest versions" to trickle down on our
> dev machines :)
>
> >
> > But is running that going to produce windows binaries rather than linux
> > ones?
> >
>
> I believe it's producing Linux binaries, not Windows ones. So probably a
> non-starter.
>
It would produce Linux binaries. It should be possible to convince it to do
Windows binaries some how. Just hoping there was a way to build DPDK
with standard tools and not having to use cygwin.
next prev parent reply other threads:[~2019-01-07 16:51 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 [this message]
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
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=20190107085125.3e3adf05@hermes.lan \
--to=stephen@networkplumber.org \
--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=mattias.ronnblom@ericsson.com \
--cc=ocardona@microsoft.com \
--cc=ranjit.menon@intel.com \
--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).