Moving discussion to -devel. By the way, are you aware that we already perform Visual Studio builds in appveyor?
https://ci.appveyor.com/project/mattock/openvpn-build/history Do you think we should have both? What would be nice to have is to trigger VS build on every commit to openvpn repo, since openvpn-build is something we run manually. ---------- Forwarded message --------- Lähettäjä: Илья Шипицин <chipits...@gmail.com> Date: su 21. heinäk. 2019 klo 18.17 Subject: Re: [Openvpn-devel] [PATCH] crypto.c: fix Visual Studio build To: Lev Stipakov <lstipa...@gmail.com> чт, 18 июл. 2019 г. в 16:26, Lev Stipakov <lstipa...@gmail.com>: > Hi, > > to 18. heinäk. 2019 klo 14.15 Илья Шипицин (chipits...@gmail.com) > kirjoitti: > >> btw, can you share steps required for Visual Studio builds ? >> > > Just clone > > https://github.com/openvpn/openvpn-build > > and run > I used to think we can run build from 'openvpn/openvpn' repo. well, openvpn-build is good as well > c:\Users\lev\Projects\openvpn-build\msvc>set MODE=DEPS&& build.bat > c:\Users\lev\Projects\openvpn-build\msvc>set MODE=OPENVPN&& build.bat > > It depends on VS2017, maybe it is time to switch to VS2019. > travis-ci comes without VS installed. I'll figure out is it legal to install community edition or not currently it already caught nasty bug "rc" was removed by endlocal: https://github.com/OpenVPN/openvpn-build/pull/152 > > >> travis-ci supports windows builds. I would like to add VS to travis-ci >> > > That would be cool. > >> > -- > -Lev > -- -Lev
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
