Agreed. I leapt a bit too far to land at my conclusion. :| I gladly defer to those who have to live with this decision in the long run.
(Unfortunately, it seems that MS' VSTS doesn't have any WDK or EWDK CI solutions at all...oh well.) -----Original Message----- From: Simon Rozman <si...@rozman.si> Sent: Tuesday, July 3, 2018 12:40 PM To: Jon Kunkee <jkun...@microsoft.com>; Илья Шипицин <chipits...@gmail.com>; Samuli Seppänen <sam...@openvpn.net> Cc: openvpn-devel <openvpn-devel@lists.sourceforge.net> Subject: RE: tap-windows6 and AppVeyor Hi, > I chose the EWDK thinking it would actually be easier for CI because it was > so > similar to the Win7 DDK, but from what you are saying I was wrong (at least > for AppVeyor). Are you interested converting buildtap.py to use > VS2017+WDK instead of the EWDK? I'm happy to do it, but I won't get to it > until next week at the earliest... EWDK is a nice step forward in simplifying the build environment. Unfortunately, a step too forward in AppVeyor's case. ;) The decision to keep EWDK, revert back to VS2017+WDK, or support both is probably best to be made by other team members working on TAP driver most. Best regards, Simon ------------------------------------------------------------------------------ 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
