Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
17261 Discussions

Command-line quartus license installation

Altera_Forum
Honored Contributor II
‎02-22-2012 11:17 PM
2,458 Views

We're having several Linux build servers, and I'm trying to integrate quartus installation into a command-line flow to automate the install/upgrade process. 

 

I've got quartus and device installation working. However, I cannot figure out the command to specify a license. 

 

Specifically, I'm interested in "30-day eval period" and "specify license file location" options.  

See the attached screenshot. 

 

The only way to get this is by running "<install dir>/bin/quartus" executable, which is a GUI application and requires running X-server. Nothing else I tried seems to work: quartus_cmd, quartus_sh, etc. 

 

Thanks, 

Evgeni
Preview file
87 KB
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎02-23-2012 12:13 AM
1,615 Views

set LM_LICENSE_FILE

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎02-23-2012 01:00 AM
1,615 Views

Setting LM_LICENSE_FILE to point to a specific license file or a floating license server does work.  

 

However, "30-day eval period" option doesn't use LM_LICENSE_FILE. Instead, it creates a file in a user directory, for example /home/user/.altera.quartus/.cy0mkjijqke  

 

Thanks, 

Evgeni
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.