Hi Simon, What system are you using to generate MSIs? Marc (CC'd) has a patch for WIX that adds support for generating ARM64 MSIs.
Are you wrapping two arch-specific MSIs in an EXE, or doing one mixed MSI? Two MSIs will be very simple to add ARM64 to, while one mixed MSI will be harder. As for tapinstall, a standalone tapinstall under VS2017 will work perfectly with what I'm building since the EWDK consumes the vcxproj and sln files directly. In other news, I should have a groundwork/cleanup PR ready today! Thanks, Jon -----Original Message----- From: Simon Rozman <si...@rozman.si> Sent: 05/02/2018 9:36 AM To: Samuli Seppänen <sam...@openvpn.net>; Jon Kunkee <jkun...@microsoft.com>; openvpn-devel@lists.sourceforge.net Cc: Marc Sweetgall <ma...@microsoft.com> Subject: RE: [Openvpn-devel] OpenVPN on ARM64 Windows Hi, > We intend to switch away from NSIS to MSI packages. I believe Simon > already did some work in there but he was rather busy for an extended > period of time. But now he is back, so migrating away from NSIS might make > sense at this point. Thoughts Simon? I have already started working on it. I am writing a tapinstall.exe utility from scratch. I am using Visual Studio 2017 for building, so this is pretty much inline with what Jon is using. Otherwise, the utility will be quite simple to build using a Makefile approach too, so it could use existing TAP driver build system as well. 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
