Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
12 years ago

QSYS output (synthesis) directory workaround?

Hello All, We recently started upgrading from SOPC builder to QSYS. There is one(...) big annoying difference between the two systems: When generating a system QSYS copies ALL files into a synt...
Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
12 years ago

--- Quote Start ---

Because SOPC builder added the files directly to the project

--- Quote End ---

Hang on, read your original request above - you wanted to avoid copying the source to the Qsys directory :)

Qsys will copy source if you use filesets that point to your HDL source. My workaround was to point the fileset to a .qip file (which gets copied), rather than the HDL. That way I can keep editing the HDL and rebuilding the system, without having to re-run Qsys (to get it to copy the modified source to its synthesis area).

--- Quote Start ---

there was no need to use any environment variables. This allowed to have multiple versions of the same source on my system - or have multiple projects with each their own copy of the source.

--- Quote End ---

If you don't like my use of environment variables, there are two other solutions;

1. The ::quartus() array is available in most of these tools. If the environment is inherited when one tool starts the next, then you can put a variable in ::quartus and access it in the downstream tools.

2. You can create a fake generic/parameter using set_parameter, and then access it later using get_parameter

Personally I see no harm in setting a few environment variables :)

Cheers,

Dave