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, your compiler executable file csc.exe is not recognized as an internal or external command.
To resolve this issue, make sure the .NET framework location is included in your PATH variable (for example, the location for .NET framework is: C:\Windows\Microsoft.NET\Framework\v4.0.30319).
A "bad key" failure
If you do not reuse your existing LM-X security configuration file for the lifetime of your application, you may get "bad key" failures between license generators, license server and licensed applications.
This issue occurs mainly when compiling LM-X SDK on multiple platforms. To resolve this problem, be sure to reuse the LM-X security configuration file.
Problem with JAVA_HOME environment variable
If your JAVA_HOME environment variable is set to the JRE rather than the JDK, or it is set to a JDK that is not officially provided by Oracle, your LM-X SDK will be built without Java programming language support. In such cases, when you build the LM-X SDK, you will see an error similar to the following:
In file included from lmxjava.c:19:0:
lmxjava.h:2:17: fatal error: jni.h: No such file or directory
#include <jni.h>
^
compilation terminated.
makefile:28: recipe for target 'all' failed
To fix this problem, make sure your environment variable is set to the path of version 1.6 or newer of the JDK.