-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
Crash on running Go-SDL2 app through Rosetta #540
Comments
Hi @SolarLune, thanks for reporting the issue! I will check if I can reproduce this and fix it. Really cool to see an actual application that uses go-sdl2! |
Hi @SolarLune, would it be possible for you to test the building for darwin/arm64 in the latest |
Hi @SolarLune, I have included static libraries for darwin/arm64 in the new |
Hello! Sorry for not getting back to you about this; other things have been going on. I'm looking to have somebody test this for me, but nobody's gotten back to me yet. Once they have, I'll let you know if the issue's resolved. Thank you for your patience! |
Hello, so another M1 user tested and said it still isn't working. Just wanted to ask if I should need to do anything apart from static compiling on Mac? |
Hi @SolarLune, was the executable statically compiled for |
Hello!
Just wanted to see if anybody knew anything about this particular issue - I'm the creator of a productivity and organization app known as MasterPlan. It's written with go-sdl2, and has been working pretty well. Normally, I build on GitHub Actions through Mac OS 10.15 - you can see the setup script for the action here.
However, some M1 Mac users have reported that the app crashes on initial startup for them - looks like it's due to sdl_ttf; this is the result that a user got on attempting to run the program through the terminal.
I've done some research on what this issue could be, but I'm not 100% on the cause. Clearly, it's crashing during the ttf.Init() function call, but I'm not really sure what to make of that. It should be that Rosetta can handle all Intel code and translate it to ARM code on program first run, right?
I could use some direction in case somebody else has run into something similar before?
The text was updated successfully, but these errors were encountered: