Changes between Version 49 and Version 50 of BuildingOnWindows
- Timestamp:
- 02/15/11 13:56:25 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildingOnWindows
v49 v50 176 176 Once OpenVPN build is finished, you may want to make an installer executable. OpenVPN installers are packaged using [http://nsis.sourceforge.net/Main_Page NSIS], which you can download from [http://nsis.sourceforge.net/Download here]. The buildsystem (win\make_dist.py) puts everything the NSI script (<openvpn-sources>\win\openvpn.nsi) needs to ''<openvpn-sources>\dist''. If you are using signed TAP drivers from an existing OpenVPN installer, you need to do one extra step: place the signed TAP drivers and corresponding ''tapinstall.exe'' to ''<openvpn-sources>\dist\i386'' and ''<openvpn-sources>\dist\amd64'', respectively. Make sure 32-bit files go to ''i386'' directory and 64-bit files to ''amd64'' directory. 177 177 178 OpenVPN installer is driven by the ''<openvpn-sources>\win\openvpn.nsi'' NSI script, which is loaded to the ''MakeNSIS'' application to generate an installer. If the ''<openvpn-sources>\dist'' directory has been properly set up, you should not encounter any errors. However, if MakeNSIS complains about something, make sure the directory layout of ''<openvpn-sources>\dist'' is like this:178 OpenVPN installer is driven by the ''<openvpn-sources>\win\openvpn.nsi'' NSI script, which is loaded to the ''MakeNSIS'' application to generate an installer. If the ''<openvpn-sources>\dist'' directory has been properly set up, you should not encounter any errors. However, if ''MakeNSIS'' complains about missing files, make sure the directory layout of ''<openvpn-sources>\dist'' contains all packaging depencies: 179 179 180 180 * '''amd64'''