DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anand Rawat <anand.rawat@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] HelloWorld example for Windows
Date: Tue, 5 Mar 2019 15:43:46 -0800	[thread overview]
Message-ID: <d71e2000-66c7-ea3f-c508-3f656a76a943@intel.com> (raw)
In-Reply-To: <CAJFAV8ya5Qmuxa0apGzDLe6bcrSr6bjCG5=hVxFHw8k4pW91fg@mail.gmail.com>

On 3/4/2019 2:13 AM, David Marchand wrote:
> 
> 
> On Fri, Mar 1, 2019 at 2:48 PM Bruce Richardson 
> <bruce.richardson@intel.com <mailto:bruce.richardson@intel.com>> wrote:
> 
>     On Thu, Feb 28, 2019 at 11:18:41PM -0800, Anand Rawat wrote:
>      > Helloworld example for Windows.
>      > Includes Windows-specific EAL changes and meson
>      > changes to build the code on Windows.
>      >
>      > Anand Rawat (6):
>      >   eal: eal stub to add windows support
>      >   eal: Add header files to support windows
>      >   eal: Add headers for compatibility with windows environment
>      >   eal: add minimum viable code for eal on windows
>      >   examples: Add meson changes for windows
>      >   doc: add documention for windows
>      >
>     Thanks for this, it's good to see some progress here with small
>     managable
>     patches.
> 
>     I've just tried this on my laptop using clang + meson + ninja. I see
>     some
>     warnings at the link phase due to unknown flags, but otherwise things
>     compile and link ok and I get helloworld app running and printing hello
>     from all cores. Specifying a coremask doesn't seem to work though -
>     perhaps
>     something to look at for a V2.
> 
> 
> Some easy warnings to fix:

This will be fixed in v2.
-- 
Anand Rawat

      parent reply	other threads:[~2019-03-05 23:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01  7:18 Anand Rawat
2019-03-01  7:18 ` [dpdk-dev] [PATCH 1/6] eal: eal stub to add windows support Anand Rawat
2019-03-01 14:03   ` Thomas Monjalon
2019-03-01 14:17     ` Bruce Richardson
2019-03-01 14:30       ` Thomas Monjalon
2019-03-01 15:19       ` Luca Boccassi
2019-03-01  7:18 ` [dpdk-dev] [PATCH 2/6] eal: Add header files to support windows Anand Rawat
2019-03-01  7:18 ` [dpdk-dev] [PATCH 3/6] eal: Add headers for compatibility with windows environment Anand Rawat
2019-03-01  7:18 ` [dpdk-dev] [PATCH 4/6] eal: add minimum viable code for eal on windows Anand Rawat
2019-03-01  7:18 ` [dpdk-dev] [PATCH 5/6] examples: Add meson changes for windows Anand Rawat
2019-03-01  7:18 ` [dpdk-dev] [PATCH 6/6] doc: add documention " Anand Rawat
2019-03-01 19:02   ` Stephen Hemminger
2019-03-02  2:41     ` Ranjit Menon
2019-03-06  8:33       ` Thomas Monjalon
2019-03-01 13:47 ` [dpdk-dev] [PATCH 0/6] HelloWorld example for Windows Bruce Richardson
2019-03-04 10:13   ` David Marchand
2019-03-04 10:14     ` David Marchand
2019-03-05 23:43     ` Anand Rawat [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=d71e2000-66c7-ea3f-c508-3f656a76a943@intel.com \
    --to=anand.rawat@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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).