Hi,

> This patch enables building openvpn with Visual Studio 2017.
>
> It is advised to use openvpn-build/msvs/build.bat which
> also downloads and build required dependencies.

I was very delighted to see this contribution. However, after hours of 
struggling to compile and prepare pre-requisites, I gave up my attempts to 
test this patch. The openvpn-build/msvc/build.bat was indeed helpful, though a 
bit outdated to be directly usable. I managed to compile all pre-requisites 
but one: pkcs11-helper. It requires autoconf. Tried with autoconf for Windows 
from Git bash (about the only one I got on my Windows) and it throws an error 
I couldn't understand what Perl and/or Bash were missing. Copied one missing 
file from its .in template and manually replacing @XY@ variables only to find 
out new missing files over and over again. Finally, I gave up. Any 
suggestions?

Now, I have begun to question the rationale of this patch... If it is too hard 
to setup building environment for me (Visual Studio is my daily working 
environment from 1998), I question its use to other Windows developers.

Would have been nice to add Windows 10 ARM64 support, but remembered somebody 
needs to compile pre-requisites for ARM64 nightmare...

BTW, I have a patch in my forked repo re-establishing Visual Studio 2017 
support for compiling openvpnserv.exe. I needed it to debug while developing 
support for multi-instances. Unfortunately, I didn't see much added value for 
the rest of the world to post it here. This one was much nicer to get working 
in VS2017, since it has no external pre-requisites.

Best regards,
Simon


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to