In http://www.alteraforum.com/forum/showthread.php?t=21510 a scheme for having a .QIP included is illustrated and I used that same technique with success in conjunction with SOPC builder.
SOPC Builder nicely just added that .QIP file by reference into the .QIP file it generated for the SOPC. In that way using the location of .QIP file itself with ::quartus(qip_path) was an effective way of locating where the heck you were in the file-system.
With QSYS it now seems that the .QIP file along with the other custom component files are copied to the folder tree where QSYS is generating HDL output. And so the result is that the ::quartus(qip_path) is, well, not all that helpful in my situation.
Is there a reasonable way to have a custom component that, instead of specifying lots of supporting files, instead specifies a 'library path' to be included so that when the custom component is analyzed the supportingn 'library' files are found automatically?
And preferably a scheme that works for both QSYS and SOPC Builder.
TIA,
Dave
