Failure to build LM-X SDK on Windows Vista
For Windows Vista, you can build the LMX-SDK only if you have administrative privileges, because the User Account Control (UAC) requires increased security.
If you do not have administrative privileges, running nmake may result in an error similar to the following:
Microsoft (R) Program Maintenance Utility Version 8.00.50727.762 Copyright (C) Microsoft Corporation. All rights reserved. ... if exist lib\lcodedata_mdd.obj del lib\lcodedata_mdd.obj if exist lib\lcodedata.c del lib\lcodedata.c cd lib ..\lmxdev -genlinkfile ..\config\xformation.lmx NMAKE : fatal error U1045: spawn failed : No error Stop.
To resolve this issue, make sure you have administrative privileges.
Failure to run nmake on Windows
If nmake fails under Windows, the compiler environment for Visual Studio may not be set up properly.
To set it on the command line, you can run vcvars32.bat, typically located in C:\Program Files\Microsoft Visual Studio version#\VC\bin. Be sure to use the same console to execute nmake that you used to run the batch file.
C#(csc.exe) errors with .NET framework
If you get C# (csc.exe) errors, make sure the .NET framework location is included in your PATH variable. For example:
- For Visual Studio 2008: C:\WINDOWS\Microsoft.NET\Framework\v3.5.
- For Visual Studio 2010: C:\Windows\Microsoft.NET\Framework\v4.0.30319.
- For Visual Studio 2012: C:\Windows\Microsoft.NET\Framework\v4.0.30319.