Starting from version 2.4, InTime introduced an automated method of configuring toolchains and licenses. InTime is able to read existing environment variables and use any toolchain that has been set up in that environment. When starting InTime, use a new command argument -tc <toolchain name>, where <toolchain name> is: "quartusii", "quartuspp", "ise", "libero" or "vivado" depending on the FPGA tool that you have configured.
[user@host]$ source /mnt/opt/Xilinx/2016.1/Vivado/2016.1/settings64.sh [user@host]$ /mnt/opt/tools/intime/intime.sh -tc vivado
After InTime starts, go to File > Settings > Vendor Toolchain... to see that the desired tool has been automatically registered.
Here is another way for a toolchain that does not need the user to 'source' an included script. You can also automate the following commands in .bashrc or other script.
[user@host]$ TOOL=/mnt/opt/Altera/16.0.0/quartus/bin [user@host]$ export PATH=$TOOL:$PATH [user@host]$ export LM_LICENSE_FILEemail@example.com [user@host]$ /mnt/opt/tools/intime/intime.sh -tc quartusii
After InTime starts, go to File > Settings > Vendor Toolchain...
Note: InTime reads and applies the LM_LICENSE_FILE environment variable from the shell where InTime was invoked.
The -tc <toolchain name> argument overrides all previously-configured toolchain settings.
If you would like to revert to a previously-configured toolchain, exit InTime and start InTime without the -tc <toolchain name> argument.
- Linux Operating System
- Windows Operating System
Knowledge Base ID: 201708241 - Last Review: Aug 24, 2017 - Revision: 1.0