Hi, > This sounds good. Please send patches (preferably with git-send-email, in > reasonable chunks) to the list so we can review and merge. Please rebase on > top of master. > > "Reasonable chunks" is a very subjective thing, of course :-) - in this case I'd > group the MSVC specific things into one patch (like, project files and such), > and the rest into one or more patches depending on the number of changes. > > MSVC-only things are easier to review as there won't be any impact to other > platforms or build systems, while generic "fix warning" patches have the > tendency to introduce warnings elsewhere (like, printf() format specifiers vs. > "what is a time_t" being a prime example). > > Anyway, thanks for dusting off these corners :-)
I hope I haven't over-divided things into chunks. Following your recommendations, no single chunk updates both C sources and MSVC related files. I'm afraid the [PATCH 05/13] might fail on mingw, but as mentioned in its description there are a couple of work-arounds possible. I am not comfortable with mingw to test it myself. Hence, I got this MSVC resurrection idea. I shall look into the building of openvpn.exe under MSVC in the days to come. At least to get an estimate how much work would require me to re-establish MSVC build for it as well. I have been happily using OpenVPN to connect remote computers for more than a decade. Perhaps it's time now to give something in return. :) Best regards, Simon
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ 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
