4.1.2. LM_LICENSE_FILE Environment Variable - Intel and third-party software use the LM_LICENSE_FILE environment variable to specify the locations of license files or license servers. - 2025-12-15

Altera High Level Synthesis Compiler Pro Edition Getting Started Guide
Version
24.1
Product Type
Development Software and Tools > FPGA Design & Simulation Tools > Quartus Prime Design Software > Pro Edition
Device Families > Arria Families > Arria 10
Device Families > Agilex Families
Device Families > Agilex Families > Agilex 7 > F-Series
Device Families > Stratix Families > Stratix 10
Development Software and Tools > FPGA Design & Simulation Tools > Quartus Prime Design Software
Device Families > Agilex Families > Agilex 7
Device Families > Cyclone Families
Device Families > Arria Families
Device Families > Stratix Families
Device Families > Cyclone Families > Cyclone V
Device Families > Agilex Families > Agilex 7 > I-Series
Device Families > Cyclone Families > Cyclone 10 > Cyclone 10 GX
Device Families > Cyclone Families > Cyclone 10
Resource Type
Documentation > User Guides
ft:sourceName
DITA
Intel® and third-party software use the LM_LICENSE_FILE environment variable to specify the locations of license files or license servers. For example, both the Quartus® Prime software and the Siemens® EDA software use the LM_LICENSE_FILE variable to specify the locations of their licenses.
Note: The time it takes for your development machine to communicate with the license server directly affects compilation time. If your LM_LICENSE_FILE environment variable setting includes paths to many license servers, or if the license server is hosted in a distant locale, you will notice a significant increase in compilation time.

On Linux or UNIX systems, insert a colon (:) after each license file or license server location that you append to the LM_LICENSE_FILE environment variable.

On Windows systems, insert a semicolon (;) after each license file or license server location that you append to the LM_LICENSE FILE environment variable.

Note: When modifying the LM_LICENSE_FILE setting to include the locations of your software licenses, do not remove any existing license locations appended to the variable.