-
Notifications
You must be signed in to change notification settings - Fork 61
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
linux arm64? #64
Comments
No idea what's up with that, sorry. The zig build is currently more like an experiment, and not really "actively maintained". One problem I saw was that the executable size is a lot bigger than going through the cmake build, at least on macOS. This might have improved in the meantime with recent linker updates though. |
I came across the same situation where I needed the sokol-shdc tool for arm64 linux. I did not encounter the problems by @pfgithub and got an executable via |
@DctrNoob you could try |
@floooh Thanks for the tip. Under Linux this still leads to an executable of 124 MB for me. Better but still pretty awful. =) |
Hmm ok, I guess I should add a "native" linux-arm64 executable (should be much easier now with the GH Actions based compilation (e.g. https://github.com/floooh/sokol-tools/actions/runs/2282914956). I "just" need to figure out how to cross-compile an arm64 executable with cmake (on macOS this is a special cmake variable |
PS: did you try stripping the executable? Maybe it still has some sort of symbols embedded despite compiling with -Drelease-small? |
@floooh I would but I am a zig noob and the |
@floooh So I figured it out. I simply had to add I could raise a PR if you like. |
@DctrNoob nice! I just added this fix (exe.strip will be set to true in any of the release modes). On macOS it doesn't seem to make much of a difference though (I still get a 12 MByte executable), but this could be because the new Zig linker doesn't implement the same tricks yet as the Apple linker. |
I tried to build with
zig build
but got an errorThe text was updated successfully, but these errors were encountered: