Honored Contributor
Honored ContributorThanks for the replies.
It's my task to setup up something to enable the designers in the company to quickly run a quartus build of the designs. I must mention that I'm from the ASIC (Synopsys DC etc) world and new to FPGA tool world. The concept of a gui is a strange one. To this end what I've basically done is produce an executable script which basically consists of... # -- project_new etc quartus_sh -t setup.tcl quartus_map --read_settings_files=on --write_settings_files=off $BUILD -c $REVISION quartus_fit --read_settings_files=off --write_settings_files=off $BUILD -c $REVISION quartus_sta -t timequest_run.tcl As you can see the only tcl I'm using is that to set up the project up and one to pass to TimeQuest to produce the custom reports. I've not actually come across any reason to pass anything to 'map' and 'fit' yet but I thought I'd do it this way instead of using quartus_sh --flow just in case in the future I did. From what you are saying you have never needed this ability or it can be done with a script and 'quartus_sh --flow'. The problem I'm trying to solve is: I'm trying to add something between the quartus executables that will exit the script on the event of errors and give the user a clear indication of the cause. Maybe I should us quartus_sh --flow after all.
