[dpdk-dev] [PATCH v4 7/8] doc: add documention for windows

[Bruce Richardson]

On Sat, Mar 23, 2019 at 04:51:27PM +0000, Jerin Jacob Kollanukkaran wrote:
> On Fri, 2019-03-22 at 15:55 -0700, Anand Rawat wrote:
> > Added documentation to build helloworld example
> > on windows using meson and clang. Updated the
> > maintainers list to include windows maintainers.
> > 
> > Signed-off-by: Pallavi Kadam <pallavi.kadam at intel.com>
> > Signed-off-by: Anand Rawat <anand.rawat at intel.com>
> > Reviewed-by: Jeff Shaw <jeffrey.b.shaw at intel.com>
> > Reviewed-by: Ranjit Menon <ranjit.menon at intel.com>
> > ---
> > 
> > +Install the Linker
> > +------------------
> > +
> > +Download and install the Build Tools for Visual Studio to link and
> > build the files
> > +on windwos, from `Microsoft* website <
> > https://visualstudio.microsoft.com/downloads>`_.
> 
> 
> # I think, Build tools does not have link.exe. Based on my testing, I
> need to install Micro soft Visual studio community edition get the
> link.exe.
> 
> For instance, in my case, link.exe is installed in following URL in
> Visual Studio, not anywhere in build tools path.
> 
> C:\Program Files (x86)\Microsoft Visual
> Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64
> 
> If it is correct then doc needs to be updated.
> 
> # I could compile and run the dpdk-helloworld.exe, Are following
> warnings expected?
> 
> [16/16] Linking target examples/dpdk-helloworld.exe.
> clang.exe: warning: argument unused during compilation: '-pthread' [-
> Wunused-command-line-argument]
> LINK : warning LNK4044: unrecognized option '/O1'; ignored
> LINK : warning LNK4044: unrecognized option '/-no-as-needed'; ignored
> LINK : warning LNK4044: unrecognized option '/-start-group'; ignored
> LINK : warning LNK4044: unrecognized option '/-end-group'; ignored
> LINK : warning LNK4044: unrecognized option '/-no-as-needed'; ignored

Yes, they are, and, in my investigations anyway, I haven't found any way to
get rid of them. The meson support for windows is very much targetted at
users of msvc and clang-cl (which uses the msvc-style flags) rather than
regular clang, so the support is not as clean as I would like. Thankfully,
though, it does appear to be working thus far! :-)