Changes between Version 26 and Version 27 of BuildingOnWindows

Timestamp:

11/04/10 09:40:38 (13 years ago)

Author:

Samuli Seppänen

Comment:

--

BuildingOnWindows

@@ -84 +84 @@
 }}}
 
-''In theory'' this should work. However, you'll most likely encounter issues with (trivial?) compiler warnings stopping the entire build. To circumvent this remove the ''/WX'' flag in the makefile as suggested in ''INSTALL.W32'' file. This is harder than it seems for two reasons:
-
- * The correct makefile is ''ms\ntdll.mak'' (not the ''Makefile'' in build root)
- * You need to use ''Wordpad'' or other UNIX linefeed-aware editor to open and save the makefile
-
-You may also encounter issues with an incorrect target processor architecture being used by the linker, especially if you're building OpenVPN on a virtual machine:
-
-{{{
-fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
-}}}
-
-You can check the processor architecture with a tool like [http://www.gtopala.com/ SIW]. Once you know the proper target architecture you need to define it manually. If you have integrated OpenVPN to Visual Studio's graphical development environment, you can set in project properties. If you're just running the VC command-line tools, you can either append the correct architecture via [http://msdn.microsoft.com/en-us/library/y0zzbyt4%28v=VS.80%29.aspx linker options] to the build command-line or define it in environment variables: 
-
- * http://msdn.microsoft.com/en-us/library/wk97ab1b%28v=VS.80%29.aspx
- * http://msdn.microsoft.com/en-us/library/y0zzbyt4%28v=VS.80%29.aspx
-
 = Preparing the source tree for building =
 
@@ -148 +132 @@
 If you wish to use Windows for OpenVPN development integrating Git with Visual Studio (2008) may make sense.
  
+= Troubleshooting =
+
+== Compiler warnings during OpenSSL build ==
+
+When building OpenSSL you're most likely encounter issues with trivial compiler warnings stopping the entire build. To circumvent this remove the ''/WX'' flag in the makefile as suggested in ''INSTALL.W32'' file. This is harder than it seems for two reasons:
+
+ * The correct makefile is ''ms\ntdll.mak'' (not the ''Makefile'' in build root)
+ * You need to use ''Wordpad'' or other UNIX linefeed-aware editor to open and save the makefile
+
+== Wrong processor architecture during OpenSSL build ==
+
+Second problem you may encounter is incorrect target processor architecture being used by the linker:
+
+{{{
+fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
+}}}
+
+You can check the correct processor architecture with a tool like [http://www.gtopala.com/ SIW]. Once you know the proper target architecture you need to define it manually. If you have integrated OpenVPN to Visual Studio's graphical development environment, you can set in project properties. If you're just running the VC command-line tools, you can either append the correct architecture via [http://msdn.microsoft.com/en-us/library/y0zzbyt4%28v=VS.80%29.aspx linker options] to the build command-line or define it in environment variables: 
+
+ * http://msdn.microsoft.com/en-us/library/wk97ab1b%28v=VS.80%29.aspx
+ * http://msdn.microsoft.com/en-us/library/y0zzbyt4%28v=VS.80%29.aspx
+
+Probably the easiest fix is to set the environment variable from the command-line:
+
+{{{
+c:\openssl-0.9.8o> set LINK=/MACHINE:x86
+}}}
+
+== Linker can't find link.obj ==
+
+During OpenSSL build the linker will look for object files from directories specified by environment variable ''TMP'' or ''TEMP''. By default, both are set to ''%USERPROFILE%\Local Settings\Temp''. However, if you have Cygwin installed, the chances are that it has a different idea about where to put temporary files. You can verify this with the ''env'' command:
+
+{{{
+c:\openssl-0.9.8o> env
+--- SNIP ---
+
+TMP=/tmp
+TEMP=/tmp
+
+--- SNIP ---
+
+TERM=cygwin
+}}}
+
+Unfortunately these environment variables can't be set manually with ''set'' command.
+
+
 = External links =