176 | | Once OpenVPN build is finished, |
| 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 something, make sure the directory layout of ''<openvpn-sources>\dist'' is like this: |
| 179 | |
| 180 | * '''amd64''' |
| 181 | * OemWin2k.inf |
| 182 | * tap0901.cat |
| 183 | * tap0901.sys |
| 184 | * tapinstall.exe |
| 185 | * '''bin''' |
| 186 | * Microsoft.VC90.CRT |
| 187 | * msvcr90.dll |
| 188 | * Microsoft.VC90.CRT.manifest |
| 189 | * libeay32.dll |
| 190 | * libpkcs11-helper-1.dll |
| 191 | * libpkcs11-helper-1.dll.manifest |
| 192 | * openssl.exe |
| 193 | * openvpn-gui-1.0.3.exe |
| 194 | * openvpn.exe |
| 195 | * openvpnserv.exe |
| 196 | * ssleay32.dll |
| 197 | * '''i386''' |
| 198 | * OemWin2k.inf |
| 199 | * tap0901.cat |
| 200 | * tap0901.sys |
| 201 | * tapinstall.exe |
| 202 | * '''samples''' |
| 203 | * client.ovpn |
| 204 | * sample.ovpn |
| 205 | * server.ovpn |