From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id D9389A0679 for ; Tue, 2 Apr 2019 03:01:08 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 94F7A4C93; Tue, 2 Apr 2019 03:01:07 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id D23DE4C8F for ; Tue, 2 Apr 2019 03:01:05 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Apr 2019 18:01:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,298,1549958400"; d="scan'208";a="132129820" Received: from unknown (HELO [10.241.225.91]) ([10.241.225.91]) by orsmga006.jf.intel.com with ESMTP; 01 Apr 2019 18:01:04 -0700 To: Thomas Monjalon , Anand Rawat Cc: dev@dpdk.org, ranjit.menon@intel.com, jeffrey.b.shaw@intel.com, bruce.richardson@intel.com, harini.ramakrishnan@microsoft.com References: <20190306041634.12976-1-anand.rawat@intel.com> <20190328232451.16988-1-anand.rawat@intel.com> <20190328232451.16988-8-anand.rawat@intel.com> <111013680.KhI2ai8QQM@xps> From: Pallavi Kadam Message-ID: <5ae88ef9-e353-c106-683e-94ae90c83ce4@intel.com> Date: Mon, 1 Apr 2019 18:01:04 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <111013680.KhI2ai8QQM@xps> Content-Type: text/plain; charset="UTF-8"; format="flowed" Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v7 7/8] doc: add documentation for windows X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190402010104.QOFNCOoX9DyDfCusgMAGNGr3eTzB1a1DHaAR3DDOycU@z> On 4/1/2019 4:22 PM, Thomas Monjalon wrote: > 29/03/2019 00:24, Anand Rawat: >> Added documentation to build helloworld example >> on windows using meson and clang. Updated the >> maintainers list to include windows maintainers. > [...] >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> +Windows support >> +M: Harini Ramakrishnan >> +M: Omar Cardona >> +M: Anand Rawat >> +M: Ranjit Menon >> +F: lib/librte_eal/windows/ > This change should be in the first patch (when introducing eal/windows). > In this doc patch, you should add > F: doc/guides/windows_gsg/ Ok, will be done in the coming patch v8. > > [...] >> +The DPDK and its applications require the Clang-LLVM* C compiler and MSVC* linker. >> +The Meson* Build system is used to prepare the sources for compilation with the Ninja backend. >> + >> +\*Other names and brands may be claimed as the property of others. > This sentence looks weird. What does it mean? Thought of adding asterisk in front of names and brands those are claimed from other websites/ organizations for instance, MSFT, LLVM. Can be removed, if not required. > > [...] >> +Download and install the clang compiler from `LLVM* website `_. > Why is there an asterisk after LLVM? As the link has been copied from LLVM website (other property). Can be removed, if not required. > > [...] >> +Download and install the Build Tools for Visual Studio to link and build the files on windows, from `Microsoft* website `_. >> +When installing build tools, select the "Visual C++ build tools" option and ensure the Windows SDK is selected. > Please try to limit the line length. > We are supposed to not exceed 80-chars if possible. > The best is to wrap lines logically (as in code) > after a comma or a point, etc. Will limit the line length in v8. > > [...] >> + cd C:\Users\me\dpdk\build >> + helloworld.exe >> + hello from core 1 >> + hello from core 3 >> + hello from core 0 >> + hello from core 2 > That's definitely a good goal for release 19.05! > >> +Limitations >> +=========== >> + >> +DPDK for Windows is currently a work in progress. Not all DPDK source files >> +compile. Support is being added in pieces so as to limit the overall scope >> +of any individual patch series. The goal is to be able to run any DPDK >> +application natively on Windows. > Yes > >