Closed markusdd closed 4 years ago
I can then open a fresh terminal and type gtkwave, which will go through, but MacOS will complain about security, so I have to abort, allow it and then click open, it will then start.
That’s a macOS security feature. If you don’t want the protection, install with the --no-quarantine
flag.
The rest of your issue is unrelated to Homebrew Cask, but to the tool itself, so you need to ask upstream.
General troubleshooting steps
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
I'm installing gtkwave using brew cask install gtkwave. It creates a link in /usr/local/bin to the embedded bin_launcher script. I can then open a fresh terminal and type gtkwave, which will go through, but MacOS will complain about security, so I have to abort, allow it and then click open, it will then start. Also choosing the app launcher from GUI works from then on. From CLI though I will get the error below.
I am aware that I can add the path /Applications/gtkwave.app/Contents/Resources/bin/ to my env (from the link in the Caveats), but then I am overriding the gtkwave command with the perl script in the package. Launching gtkwave then works after installing the perl package, but e.g. rtlbrowse will complain like this:
I actually want to build a rather generic project build and gui startup flow, and wish to avoid ugly hardcoded mac specific paths. This should run on linux as well. So I would hope to just be able to call gtkwave, rtlbrowse, xml2stems in the scripts. Requiring other users or machines to patch their environments aside from installing the tools is usually a big ask and I do not know why gtkwave and related binaries are such a big hassle to install on Mac. icurus verilog, verilator etc. do not have these issues.
So all in all my questions are: Whats the purpose of the linked bin_launcher script if it always fails? Why are the other essential binaries not put into the path? What would be the recommended way to proceed?
Usuallly all other homebrew packages are a nice batteries included experience, but gtkwave is very different (I will say situation on Fink and Macports is not better).
Don't hesitate to ask if you have other questions.
Command that failed
Output of command with
--force --verbose --debug
Output of
brew cask doctor
Output of
brew tap