| 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 | | |
| 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: |
| | 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''. However, there are still (as of OpenVPN 2.2-rc) a few manual steps involved: |
| | 177 | |
| | 178 | * 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. |
| | 179 | * You need to [http://msdn.microsoft.com/en-us/library/ms235591%28v=vs.80%29.aspx manually embed manifest files] to ''openvpn.exe'', ''openvpnserv.exe'', ''lzo2.dll'' and ''libpkcs11-helper-1.dll''. The purpose of the manifest file - whether embedded or not - is to declare the run-time dependencies of the EXE/DLL. This step is required because the NSI script is not configured to copy external manifest files to the installer package. |
| | 180 | |
| | 181 | 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 ''<openvpn-sources>\dist'' directory contains all of the packaging dependencies: |
