Visible to Intel only — GUID: ewa1462816558670
Ixiasoft
1. Intel® High Level Synthesis (HLS) Compiler Pro Edition Getting Started Guide
2. High Level Synthesis (HLS) Design Examples and Tutorials
3. Troubleshooting the Setup of the Intel® HLS Compiler
A. Intel® HLS Compiler Pro Edition Getting Started Guide Archives
B. Document Revision History for Intel® HLS Compiler Pro Edition Getting Started Guide
1.1. Intel® High Level Synthesis Compiler Pro Edition Prerequisites
1.2. Downloading the Intel® HLS Compiler Pro Edition
1.3. Installing the Intel® HLS Compiler Pro Edition for Cyclone® V Device Support
1.4. Installing the Intel® HLS Compiler Pro Edition on Linux Systems
1.5. Installing the Intel® HLS Compiler Pro Edition on Microsoft* Windows* Systems
1.6. Initializing the Intel® HLS Compiler Pro Edition Environment
Visible to Intel only — GUID: ewa1462816558670
Ixiasoft
3.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. For example, both the Intel® 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.