On Mon, Sep 13, 2010 at 8:25 PM, Peter Stuge <pe...@stuge.se> wrote: > autotools is absolutely alien in Windows, and to be honest a bit of a > hassle to set up if you're already a VS wizard.
In OpenVPN upstream provides binaries using mingw anyway. So there is no need to support any other environment for Windows. This makes it easy. Also, please keep in mind that OpenVPN is not a library... so much easier to manage. >> and the mixture of different projects: openvpn, tap, windows >> installer, easy-rsa. > > How can the installer situation be improved? I want to make an NSIS > installer as well, and I would quite like to keep it *within* the I just saying that most users do not interested in compiling the tap driver, also compiling the tap driver requires Microsoft DDK. So separating the tap into its own release management would be wise... a separate MSI for the TAP that can be embedded within other installers. Easy-rsa has nothing to do with openvpn, it is great that it is provided, but as a separate process, fix in easy-rsa should not modify openvpn release The same for Windows installer, a fix in Windows installer should not modify openvpn version, as it has nothing to do with it. Alon.
