Browse files

Updated README.win32 for compiling with VS2008 and issues with mc.exe

Visual Studio 2008 puts some things in different places and doesn't
include the Message Compiler (mc.exe).
  • Loading branch information...
Andrew Thompson Andrew Thompson
Andrew Thompson authored and Andrew Thompson committed Dec 15, 2009
1 parent 98751d5 commit 346b530950c2c6c80d179d8ff1fcc835ed95c1b8
Showing with 14 additions and 0 deletions.
  1. +14 −0 README.win32
@@ -366,6 +366,20 @@ backslashes in your path environment variable in Cygwin bash, but LIB
and INCLUDE should contain Windows style paths with semicolon,
drive letters and backslashes.
+If you wish to use Visual Studio 2008, a couple things need to be tweaked,
+namely the fact that some of the SDK stuff is installed in (by default)
+C:\Program Files\Microsoft SDKs\v6.0A . Just ensure that that
+C:\Program Files\Microsoft SDKs\v6.0A\Lib is in LIB and
+C:\Program Files\Microsoft SDKs\v6.0A\Include is in INCLUDE. A symptom of not
+doing this is errors about finding kernel32.lib and windows.h.
+Additionally, if you encounter errors about mc.exe not being found, you must
+install the entire Windows SDK (the partial SDK included in visual studio
+apparently does not include it). After installing it you'll want to add
+something like: /c/cygdrive/Program\ Files/Microsoft\ SDKs/v7.0/bin to your
+PATH to allow the environment to find mc.exe. The next Visual Studio (2010) is
+expected to include this tool.
* Sun's Java JDK 1.5.0 or higher. Our Java code (jinterface, ic) is
written for JDK 1.5.0. Get it for Windows and install it, the JRE is
not enough. If you don't care about Java, you can skip this step, the

0 comments on commit 346b530

Please sign in to comment.