libphysfs.1.dylib issue on macOS Mojave

Started by Aurelien, January 28, 2019, 12:30:18 PM

Previous topic - Next topic
Hey guys,

First of all, congratulaions on your work and thanks for putting this out with thorough tutorials and all the necessary tools. I would love to use the Solarus Quest Editor on my MacBook Pro running macOS Mojave. I downloaded the engine. Solarus and Solarus-run work but I have to maximize the window and go fullscreen or I just get the Audio and no Video (after that, I can switch back to small window mode and it works fine). But I can't launch the Solarus Quest Editor. If I dive into the package and run the solarus quest editor, here is what I get :

/Users/aurelien/Downloads/Solarus\ Quest\ Editor\ Package\ 1.6.0/Solarus\ Quest\ ; exit;
dyld: Library not loaded: @rpath/libphysfs.1.dylib
  Referenced from: /Users/aurelien/Downloads/Solarus Quest Editor Package 1.6.0/Solarus Quest
  Reason: image not found
/Users/aurelien/Downloads/Solarus Quest Editor Package 1.6.0/Solarus Quest line 5:   670 Abort trap: 6           "$dirname/../Resources/solarus-quest-editor"
Saving session...
...copying shared history...
...saving history...truncating history files...

Am I doing anything wrong or missing something?

Thanks for your help!


Are you running the latest version of Mojave? That may solve your first problem.

No idea on the second one.

January 28, 2019, 05:13:30 PM #2 Last Edit: January 30, 2019, 06:33:05 PM by MichaelNG789
Same thing with me. It doesn't open. 10.14.2 is the latest version right?
I'm sure it will get fixed soon, but for now, I just created a prefix for the Windows version with WineBottler and am running it that way for the time being.

Edit: Now latest is 10.14.3

Thanks for your reply. I am indeed running the latest update of Mojave. I managed to fix this though. I opened the Solarus package and copied the libphysfs.1.dylib into the Solarus Quest Editor package. Works perfectly now.

Nice Fix! I guess you can change it to [SOLVED] now right?

I've got the same problem on my end too, though my Mac OS version is on High Sierra (10.13.4). I'll do that fix and see if it works out!

This is now fixed in the official download. Thanks for reporting the problem!