> 2012/2/27 Samuli Seppänen <sam...@openvpn.net>: >>> Hello, >>> >>> A repository is available[1], stripped down with only tap sources. >>> >>> To build use you need ddk available: >>>> configure >>>> build >> Checked out the sources using "Git Bash", then ran the commands from a >> (non-admin) Visual Studio 2008 command prompt. Got these errors: >> >> <http://pastebin.com/XfZDJPpa> > Please remove the @echo off for me to see the files. > You can also look into it... It simply look for files to substitute vars in. I'll look into this in detail later, I just briefly tested it.
>>> It builds winxp 32bit and win7 64bit I hope this is what the current >>> installer is doing, >>> as building the tap is kept secret. >> Actually, the TAP-driver is built using the Python build scripts in the >> "win" subdirectory. Those scripts build both 32-bit and 64-bit drivers. > Yes. > But something is not right there as far the signing goes. That is correct. James has a Python wrapper module that handles signing using signtool.exe, but for one reason or another, he can't release it. >>> In the open source package we will provide vanilla devcon and not the >>> modified >>> tapinstaller which we do not have the sources of. I it is so important >>> to hack computer >>> and bypass Windows confirmation dialog. >> The Python-based buildsystem also builds tapinstall.exe/devcon.exe. It >> looks for the sources from ../tapinstall by default (see "grep T1SRC >> win/*"). The sources are standard devcon sources; the resulting binary >> is simply renamed to "tapinstall.exe". > There is no T1SRC in master. Oops, a typo. TISRC, not T1SRC. It's defined in win/settings.in. > There is no point in compiling devcon if it is provided in DDK. > What james done in the past is to modify the sources to override the > sign warning message. > I provide devcon as-is and let user override it if needed. Ah, ok, didn't know that. Sounds good. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
