Note
*safety-qualified Arm Compiler is also known as certified Arm Compiler
This page presents the different usage scenarios for Arm Compiler toolchains, describing which license is used in each case and any required configuration steps. Throughout this page, "Arm Compiler toolchain" refers to the following products:
This page assumes you know already which version of Arm Compiler to use and focuses on licensing and IDE integration aspects. You can download Arm Compiler packages from the Arm Compiler downloads page.
In this use case, your Arm Compiler toolchain runs without any of the IDEs listed below installed alongside it.
Typical scenarios include:
Because the Arm Compiler toolchain runs standalone, you need to supply additional information - normally supplied by the IDE - so that Arm Compiler can find the appropriate product license. The configuration item common to all use cases is to set the ARMLMD_LICENSE_FILE
environment variable to point at your license file(s) and/or license server(s). The next configuration steps to take depend on the license you have or want your Arm Compiler toolchain to use.
Note: all environment variables listed in this section apply to the machine and environment where Arm Compiler runs. These are unrelated to the configuration of your license server, if you have one.
In this use case, the Arm Compiler toolchain is used within the IDE supplied by Arm, as part of one of our tools suites.