Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

Multiple Quartus releases on Linux - How to choose from command line

Altera_Forum
Honored Contributor II
1,376 Views

I have a Linux (CentOS 6.8) server with multiple users (connected through ThinLink) and multiple Quartus versions installed.  

I have created a file in /etc/profile.d/ that adds the install path for the various Quartus versions to all users. 

 

http://www.alteraforum.com/forum/attachment.php?attachmentid=13180&stc=1  

 

http://www.alteraforum.com/forum/attachment.php?attachmentid=13181&stc=1  

 

 

The challenge is that when starting Quartus from command line, it is the last added path in the .sh file that is executed. In the above example Quartus Prime Standard is started.  

(In this case I could of course differentiate by typing either quartus or qpro, but that is not the point here...) 

 

Is there a way of selecting which Quartus version to start from what is present in the $PATH variable? 

 

Is there a smarter way of doing this than using profile.d?
0 Kudos
1 Reply
Altera_Forum
Honored Contributor II
651 Views

I'd say avoid putting both paths at the same time. First, it won't work as expected, and second, users could have weird results. 

 

One solution could be putting two small scripts in /etc/skel, one for each Quartus version. Each newly created user will receive copies of them in their home directory (or just copy for already existing users). Then upon login the user would "source" the preferred version's script from $HOME. 

And it's not just about paths, there are some other env settings that Quartus expects. Local copies of the scripts are good idea, so each user would modify to their needs.
0 Kudos
Reply