Changes between Version 51 and Version 52 of BuildingOnWindows


Ignore:
Timestamp:
02/15/11 14:08:40 (13 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildingOnWindows

    v51 v52  
    177177
    178178 * 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.
     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 does not include external manifest files.
    180180
    181181OpenVPN 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:
     
    247247  * [http://www.gtopala.com/ System Information for Windows]: a useful tool for debugging processor architecture issues
    248248  * [http://www.dependencywalker.com/ Dependency Walker]: a tool to debug DLL issues in DLLs and EXEs
     249  * [http://weblogs.asp.net/kennykerr/archive/2007/07/10/manifest-view-1-0.aspx Manifest view]: a tool to view contents of embedded manifests in EXEs and DLLs