Hi, I was dismissed by the AppVeyor about an image preinstalled with EWDK request. They explained I can use their build cache to maintain a local EWDK copy. Unfortunately, the build cache is account-specific, meaning every user trying to run its own fork (including OpenVPN for upstream) will require AppVeyor Premium plan. EWDK won't fit into 1GB build cache limit with Free/Basic plan.
So, we still have Jon's alternative proposal to support EWDK *and* VS2015+WDK building in buildtap.py. The downside to this approach is, we are using slightly different build environment for CI. Best regards, Simon > -----Original Message----- > From: Jon Kunkee <jkun...@microsoft.com> > Sent: Friday, June 15, 2018 7:58 PM > To: Илья Шипицин <chipits...@gmail.com>; Samuli Seppänen > <sam...@openvpn.net> > Cc: Simon Rozman <si...@rozman.si>; openvpn-devel <openvpn- > de...@lists.sourceforge.net> > Subject: RE: tap-windows6 and AppVeyor > > Hi, > > I like the idea of asking AppVeyor if they could include the EWDK in one of > their images. It is a standalone tool, so Visual Studio is not needed. > > Sadly I don't see a Chocolatey package for the EWDK. That would have been > convenient. > > The AppVeyor docs[1] say that the Visual Studio 2017 image in AppVeyor > already has the Windows Driver Kit (WDK) installed. Buildtap.py would need > a couple of changes to consume the WDK instead of the EWDK, but it is an > option. > > Thanks, > Jon > > [1] https://www.appveyor.com/docs/build-environment/
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
