A user who is new to InTime needs to configure its license. This process can be automated by the tools/IT administrator.
InTime reads and applies the LM_LICENSE_FILE environment variable from the shell where InTime was invoked.
The following example shows a typical approach to saving the LM_LICENSE_FILE variable to a file and then applying it before starting InTime.
- email@example.com points to your FPGA tool's license server.
- firstname.lastname@example.org, point to your InTime/License Server.
'source'-ing the file as seen below saves you the trouble of looking up LM_LICENSE_FILe every single time and is probably what most people are doing.
Taking it further, your administrator can add this LM_LICENSE_FILE environment variable to the intime.sh/intime.bat script so that users do not need to 'source' the mylicense file when starting InTime.
[user@host]$ cat /mnt/tools/plunify/intime/mylicense export LM_LICENSE_FILEemail@example.com:firstname.lastname@example.org [user@host]$ source /mnt/opt/plunify/intime/mylicense [user@host]$ /mnt/opt/plunify/intime/intime.sh
After InTime starts, go to File > Settings.. > Run Targets
If done correctly, the intended InTime / License Server information will be displayed.
Note: In a Linux environment, multiple license servers are separated by ":". In a Windows environment, the separator is a ";".
There can only be one InTime/License Server specified in the LM_LICENSE_FILE environment variable.
- Linux Operating System
- Windows Operating System
Knowledge Base ID: 201909011 - Last Review: Sep 01, 2019 - Revision: 1.0