sh: ghdl: command not found
branylagaffe opened this issue · 8 comments
When i try to compile a VHDL file on my OSX 10.11, i got this:
sh: ghdl: command not found
[E] Compilation failed!
(vsim:4309): Gtk-CRITICAL **: gtk_entry_set_text: assertion 'text != NULL' failed
GHDL was installed with brew, do you think it can mess up with the wrapper ?
What happens when you open a standard shell and type ghdl? Does it recognize it here?
If not, try to find out where the ghdl binary resides on your system and add it to the system path. A quick Google told me this can be done by adding this to the ~/.bash_profile file on Mac:
export PATH="$PATH:/path/to/ghdl"
Restart the related programs afterwards.
I've also been wanting to add a feature to the wrapper which allow the user to specify the path of GHDL. Might do that, but you'd still have to find out to where brew installed ghdl.
i can access to the ghdl binaries through a shell, i'm going to try to build it from the github repo
Hmmm that's weird... if it works on the shell, the wrapper should have no problem using it either.
Do you use model-ghdl from the shell or do you use it from an IDE (such as Sigasi)? If it's the latter, try starting the IDE from a shell where ghdl works and try again.
I use it from Sigasi, and even if I build GHDL with the lattest dev build, i got the same error.
I will try to invoke the sigasi from the shell
Okay, I opened Sigasi with open /Applications/Sigasi\ Studio.app/
now it lunchs the modal box to select the simulation time, but the windows is not on top of all the windows (mini issue here ^^)
I'm going to try with a testbench, to assess if it correctly work if the IDE is open from the shell
Does it always launch in the background or only sometimes? I'll take a look at if I can fix this tomorrow.
Should you get some error from ghdl when launching the simulation, you can try adding the -no-precompile flag to the vcom args in the Sigasi prefs. I've seen some weird problems with the compile-on-vcom feature in the past.
nice ! My code still doesn't compile, i may open an another issue if the wrapper is the caus