...
- If you are installing LM-X License Manager for the first time: The LM-X security configuration file will be automatically created in the config directory of the SDK.
- If you are upgrading LM-X to a newer version or compiling LM-X on multiple platforms: Choose an existing LM-X security configuration file, as shown below.
Panel |
---|
|
Anchor signing signing
Step 4. (MacOS only) Provide Developer ID Application Certificate.
signing | |
signing |
Note the following:
- The Developer ID Application Certificate will be assigned to the DEVELOPER_ID_CERTIFICATE variable in the platform.mk file.
- If you did not provide a certificate during the installation process or you want to change the certificate, edit the platform.mk file and assign the correct certificate to the DEVELOPER_ID_CERTIFICATE variable, then recompile the LM-X SDK.
- See MacOS on ARM support for more information about providing a Developer ID Application Certificate.
Panel |
---|
|
Step 5. Activate the license.
Note the following:
- If you are installing LM-X License Manager for the first time: Activate your license online using your Activation Key (sent to you via email).
- If you are upgrading LM-X: Select a previously activated license file.
Panel |
---|
|
Step
...
6. Decide whether you want to compile the LM-X SDK.
Note: If you used a previously activated license file in Step 4, compile the LM-X SDK now.
Panel |
---|
|
Step
...
7. When needed, install the end-user tools.
Note (MacOS only): If a Developer ID Application Certificate was provided in Step 4, it will be used to sign the LM-X End-user Utility and LM-X License Server.
Panel |
---|
|
...