Can I specify "relative paths" for MIF files, etc?

I recommend always using relative pathnames for files that maintain a fixed directory relationship with respect to the Quartus project directory if the project is moved to a different location. Use absolute pathnames only for files that stay in the same absolute location when the project is moved.

I've experimented with this for memory initialization files in particular, but I don't remember what I figured out, and there was some sort of bug at the time that might have been fixed by now. (I think the bug had to do with using user library settings to tell Quartus where to find this kind of file.) Experiment to see how it works now (unless someone else posts the answer to that). You will have altsyncram or another memory megafunction instantiated somewhere. The instantiation will have a parameter or generic that identifies the memory initialization filename with a possible pathname shown there. The way Quartus uses a relative pathname stated at the instantiation might be relative to the directory containing the instantiating RTL file, relative to the project directory, or both (with Quartus looking for the initialization file in both locations--I think I've seen this behavior for some sort of file).

--- Quote Start ---

I recommend always using relative pathnames for files that maintain a fixed directory relationship with respect to the Quartus project directory if the project is moved to a different location. Use absolute pathnames only for files that stay in the same absolute location when the project is moved.

I've experimented with this for memory initialization files in particular, but I don't remember what I figured out, and there was some sort of bug at the time that might have been fixed by now. (I think the bug had to do with using user library settings to tell Quartus where to find this kind of file.) Experiment to see how it works now (unless someone else posts the answer to that). You will have altsyncram or another memory megafunction instantiated somewhere. The instantiation will have a parameter or generic that identifies the memory initialization filename with a possible pathname shown there. The way Quartus uses a relative pathname stated at the instantiation might be relative to the directory containing the instantiating RTL file, relative to the project directory, or both (with Quartus looking for the initialization file in both locations--I think I've seen this behavior for some sort of file).

--- Quote End ---

Hi dane, hi Brad

in the past there was some trouble with relative pathname for the MIF-files. I run run atest with Quartus 8.1 and it lookslike that the problems are solved. The MIF file is always found by the path defined in the Megawizard.

Kind regards

GPK

Thanks Brad and GPK ...

--- Quote Start ---

in the past there was some trouble with relative pathname for the MIF-files. I run run atest with Quartus 8.1 and it lookslike that the problems are solved. The MIF file is always found by the path defined in the Megawizard.

--- Quote End ---

that's what I've been afraid of. Haven't tried it yet, but this is an OLD project, and is pretty massive, and was done in QII v6.0 ... I don't want to run the risks of changing the compiler version and all that could potentially go wrong...

I ended up just putting this legacy project in the desired path on my C:\ drive .. I should only be working on it for a couple weeks to get a "fix" done and then I'll be done with it, so it's simpler to just "give in" to the desired path than try and fix (break) everything ... :)

thanks all!

..dane