-
-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
internal/graphicsdriver/metal: failed to load .framework files #2732
Comments
That's interesting. I'll take a look. Thanks, CC @TotallyGamerJet just in case. |
@lowfatcode Could you try:
? Thanks, |
Yep, that's fixed it! |
Thank you! |
Note that Oto should not have this issue as Oto already uses full paths. |
@lowfatcode By the way, have you set environment variables like echo $DYLD_LIBRARY_PATH
echo $DYLD_FALLBACK_LIBRARY_PATH
echo $DYLD_FRAMEWORK_PATH
echo $DYLD_FALLBACK_FRAMEWORK_PATH
env | grep DYDL Thanks, |
Friendly ping |
I could reproduce the issue with macOS 13.5 Ventura:
Setting the environment variable causes this issue, even without a value. |
DYLD_FALLBACK_FRAMEWORK_PATH
prevents launching on macOS
I haven't set any of those but I think the title of the Issue has been edited by someone else - I never referred to these in my original submission? |
I changed it. I thought this issue was by environment varialbes, rather than macOS 14. If this happens without setting these environment variables, this might be a bug of macOS 14. Since macOS 14 is still a beta, I was not 100% confident I should back-port the fix to the stable branch. As I found the same problem could happen with modifying environment variables with macOS 13, I 'generalized' this issue. |
Thank you for confirming the environment variables. My current guess is that macOS 14 beta has some bugs, but the latest commit already includes the fix for the 'generalized' issue (not only for macOS 14 but also macOS 13 with setting environment variables). |
Aha! No, I hadn't changed any environment variables. |
Sure! Thank you for reporting this issue again. I appreciate your feedbacks! |
Note to myself: even not setting DYLD_FALLBACK_FRAMEWORK_PATH, this issue happened with Xcode 15... Sigh |
DYLD_FALLBACK_FRAMEWORK_PATH
prevents launching on macOS
Ebitengine Version
v2.5.7
Operating System
Go Version (
go version
)1.21.0
What steps will reproduce the problem?
ebiten
reposityblur
example withgo run .
What is the expected result?
The example should start up.
What happens instead?
The following error is returned:
Anything else you feel useful to add?
It seems like the
purego
library that appears to be used to dynamically load libraries is not checking the right path. I think it should be looking in/System/Library/Frameworks/OpenGL.framework
.Perhaps this is a change introduced in Sonoma?
The text was updated successfully, but these errors were encountered: