> Would be nice to have an option for Release or debug build. User mode code > too. Right now, we are not deploying the created executables anywhere. Appveyor does have that option. We can probably enhance it once we have a in-tree windows installer.
On the release/debug question, the only option is to do both - which will increase the build time. Increase of build time means that pre-checkin check through appveyor will be slow and people may not actually use it. On the question of the pre-compiled headers, it is likely not going to help the userspace build because it is done one file at a time. I will nevertheless investigate. > > -----Original Message----- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Nithin Raju > Sent: Thursday, February 05, 2015 10:39 PM > To: Gurucharan Shetty > Cc: dev@openvswitch.org; Gurucharan Shetty > Subject: Re: [ovs-dev] [PATCH] appveyor: Build windows kernel datapath. > >> +- C:\MinGW\msys\1.0\bin\bash -lc "cd /c/openvswitch && ./configure >> CC=build-aux/cccl LD=\"`which link`\" LIBS=-lws2_32 >> --with-pthread=C:/pthreads-win32/Pre-built.2 --with-openssl=C:/OpenSSL-Win32 >> --with-vstudioddk=\"Win8.1 Release\”" > > > > Thanks for the patch. > > > > Only comment I had was to was to prefer to use "Win8.1 Debug” rather than > “Win8.1 Release”. It doesn’t make any practical difference though, but it > might be best to do “Debug” builds rather than “Release” in a build-test > setup. > > > > Acked-by: Nithin Raju <nit...@vmware.com> > _______________________________________________ > dev mailing list > dev@openvswitch.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=MQliY0lervWD1h0IE-vbsFegcFKLa9zmypMkSUENsKU&s=xwhEJXSZhbRRLtHYTw6veobMVUDNCK01EUqRgvoeOlw&e= _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
