| 95 | | If you want to build the latest development code fetch it using ''Git for Windows'' (Git shell) or ''!GitExtensions'' (GUI). Check [wiki:TesterDocumentation these instructions] to see which Git URI to use. Once you have fetched OpenVPN sources you need to customize a few variables in the ''win\settings.in'' file. Make sure to use a UNIX linefeed-capable editor such as ''wordpad''. |
| | 95 | == Preparing the build tree == |
| | 96 | |
| | 97 | If you want to build the latest development code fetch it using ''Git for Windows'' (Git shell) or ''!GitExtensions'' (GUI). Check [wiki:TesterDocumentation these instructions] to see which Git URI to use. |
| | 98 | |
| | 99 | Once you have fetched OpenVPN sources you need to copy [http://stackoverflow.com/questions/1167544/devcon-exe-driver-tool-and-openvpn DevCon.exe source code] to a directory which is preferably outside the openvpn source tree so that it does not get committed to the OpenVPN Git repository by mistake, as Microsoft would probably sue us for that. The source files can be found from ''<WINDDK_INSTALL_DIRECTORY>\<DDK_VERSION>\src\setup\devcon'', for example ''C:\WINDDK\7600.16385.1\src\setup\devcon''. If you don't modify ''win\settings.in'' you need to have a directory layout similar to this: |
| | 100 | |
| | 101 | * ''C:\openvpn-build\tapinstall\7600'': devcon.exe sources, where last part of the path depends on WinDDK's major version you got installed. |
| | 102 | * ''C:\openvpn-build\openvpn-testing'': openvpn sources fetched from git |
| | 103 | |
| | 104 | Next you probably want to customize a few variables in the ''win\settings.in'' file. Make sure to use a UNIX linefeed-capable editor such as ''wordpad''. |
