| This page refers to LM-X v4.5 and newer, which made changes to the SDK distribution. If you are using a version older than v4.5, see documentation for previous versions. |
You generate licenses using xmllicgen, as described in Generating licenses. For your protected application to compile, you need to include the lmx.h header file.
...
On Windows, multiple versions of the libraries are provided, with suffixes _mt, _mtd, _md or _mdd according to the type:
Suffix | Description | Restrictions |
|---|---|---|
_mt | Multithreaded static C/C++ runtime |
|
_mtd | Multithreaded static C/C++ debug runtime | You are not permitted to ship your software using this library. |
_md | Multithreaded dynamic C/C++ runtime |
|
_mdd | Multithreaded dynamic C/C++ debug runtime | You are not permitted to ship your software using this library. |
...
The protected application should be linked with the liblmxclient library (liblmxclient[suffix].lib on Windows or liblmxclient.a on Unix) libraries. For Windows C++ applications, you may need to link with thrownew.obj from Visual Studio to explicitly enable exceptions when using new operators. See MSDN for further details.
See the example makefiles for additional system libraries that might be required for successful linking.
The lcodedata object file is part of the liblmxclient library. This file is generated based on your security configuration file when building the LM-X distribution. See Getting Started with LM-X License Manager for information on how to build the LM-X distribution.
To make your application more secure, you should use a newly generated lcodedata object file each time you link the application, particularly whenever you update LM-X to a new version. This precaution does not apply to the license generator, because it should not be subject to attacks. Also note that it is not necessary for the license generator and the application to use the same object file.