> Hi, > > On Thu, Apr 24, 2014 at 04:05:20AM -0400, Timothe Litt wrote: >>> Uh, this is a double misinformation :-) >> It's good to know that cross-compiling is an option, though >> cross-debugging (e.g. with an interactive debugger) can be an adventure too. >> >> Source of my comment was: >> >> http://community.openvpn.net/openvpn/wiki/BuildingOnWindows, which says >>> his new build system allows building OpenVPN on Windows more easily, >>> but some parts of the build may r*equire a commercial version of the >>> Visual Studio development environment.* >>> /Visual Studio 2008 Professional/is used to build OpenVPN on Windows. >>> Note that the free Express edition might not work. >>> Full installation installs*/x86 cross-tools/*which *may cause nasty, >>> hard to debug issues*. >> (The professional tools are > $1,000 US, which is not in my budget.) >> >> You may want to reword that after validating your comment. M$'s name >> for the 'free' tools is 'express edition'. The license terms vary based >> on M$'s whims, the current statement is: >>> http://www.visualstudio.com/products/visual-studio-express-vs >>> Visual Studio Express products are available at no charge and may be >>> used for commercial, production usage subject to the license terms >>> provided with each product. For example, you can use Express for >>> Windows to create apps that you can then submit for sale in the >>> Windows Store. > Yeah, I think that page needs clarification (I think you need the commercial > edition to do code signing, which is not strictly required if you use > the pre-signed tap driver bundle), *and* it needs a pointer to the other > build system page. > Added a big fat warning to the top of the page and a pointer to current documentation. Visual Studio Express also works for driver signing - I know it because I built tap-windows6 with it a while back with no issues.
-- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
