Emulator Issues #10135
closed
Terminal: "open dolphin.app" works but "dolphin" returns "command not found"
0%
Description
Operating System: OSX 10.10.5
Processor/CPU: 1.3 GHz Intel Core i5
Video Card/GPU: Intel HD Graphics 5000 1536 MB
Memory/RAM: 4 GB 1600 MHz DDR3
I'm trying to run a program (specifically a Melee AI) on top of Dolphin, which opens it in Terminal with the "dolphin" command.
Unfortunately, this didn't work for me (I had 5.0-321), though it otherwise worked normally, opening with full functionality when I double-clicked it in the applications folder or if I did "open dolphin.app" from that directory.
So, I deleted dolphin and compiled it from source using these instructions: [[https://github.com/dolphin-emu/dolphin]]
...and I still have the exact same situation (except dolphin.app is now in /Applications/dolphin/build/Binaries). Namely, "open dolphin.app" opens it fine, but "dolphin" just returns "dolphin: command not found".
I'm not sure what's wrong with the way I downloaded/compiled Dolphin, since both the download and compilation went smoothly otherwise.
I should say I also asked this question on the Support forum, but I didn't get any substantive responses.
Thanks in advance.
Updated by ligfx about 7 years ago
The actual "dolphin" binary should be located under Dolphin.app/Contents/MacOS/ (this is how Apple likes applications to be laid out). Can you try running PATH="/Applications/Dolphin.app/Contents/MacOS/:$PATH" my_melee_ai_program?
Updated by waddledoo about 7 years ago
Interesting, I didn't know Dolphin.app was itself a folder. If I cd into /Applications/dolphin/build/Binaries/Dolphin.app/Contents/MacOS, then "open dolphin" opens it along with another terminal window, but "dolphin" still returns "command not found".
Now, I assumed this problem was independent of the particular program I'm trying to run, since the Dolphin github readme says "dolphin" should just work as a standalone command.
That said, the program I am trying to run is called "Phillip", docs here: https://github.com/vladfi1/phillip
Running PATH="/Applications/Dolphin.app/Contents/MacOS/:$PATH" phillip returns "phillip: command not found", but I suppose that's to be expected, since I cloned Phillip into a different folder. I'm still unclear about how that program works, but asking the devs there, it sounded like my issue was more dolphin-specific.
Updated by ligfx about 7 years ago
Dolphin is not installed as a standalone command on macOS (almost all GUI programs aren't).
Running with PATH="/Applications/Dolphin.app/Contents/MacOS/:$PATH" should solve the problem of finding Dolphin; any problems with the phillip command itself you should take to the Phillip devs.
Updated by waddledoo about 7 years ago
Huh. Perhaps I'm misinterpreting something here, but looking at the "Command Line Usage" section here: https://github.com/dolphin-emu/dolphin
I got the impression that "Dolphin" is supposed to be a standalone command unconditionally. If that's not the case for Mac, why doesn't it say so there?
Updated by WamWooWam about 7 years ago
Did you just type "dolphin" or "./dolphin", The "./" tells the command line to open an executable in the current directory. You'll need to do this from within /Contents/MacOS
Updated by waddledoo about 7 years ago
Can confirm that from /Contents/MacOS, "./dolphin" works, but not "dolphin." With ligfx's point, I've solved my problem, my last reply was just asking why this condition was stated on the Dolphin page since this didn't seem obvious to me.
Updated by leoetlino almost 7 years ago
- Status changed from New to Working as intended
As ligfx said, we don't install a standalone binary in the path on macOS. And on Linux, the binary name is dolphin-emu, not dolphin anyway.
Also, the readme doesn't say the binary name is "dolphin".