-
Notifications
You must be signed in to change notification settings - Fork 13
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
Link native_main statically #50
Comments
The CI we use makes it pretty easy to add flags per OS - so we can just do static linkage for the Linux builds. See
A PR would be welcome - otherwise it'll just go on my (very long) todo list :) |
Huge +1 to either fixing this with static linking, or providing Musl builds that are detected in the install script. I ran the install script and was trying to figure out why on earth |
I think it's just a single line to change in the build scripts. I have never got round to doing it is all with luck the blocks next release label will make it harder for me to forget about it. If you want it quicker than that, a PR would be welcome :) |
@klardotsh I finally got around to looking at this but it doesn't seem to work, the build is exactly the same size and it's saying that it's dynamically linked https://github.com/tridactyl/native_messenger/actions/runs/11202765381 Do you know what I'm doing wrong? Should I be building it statically using
|
Currently,
native_main
is dynamically linked withlibc
. This is almost never an issue, except formusl
users like me. Now, of course, I could just shut up and build my own executables, but, fortunately, static linkage is easy enough to propose universally:This increases the size of the binary slightly: 484K -> 523K. It should also help with reproducibility (though I doubt there are currently issues with that).
My main reservation with proposing this is that I don't know what this does on systems that aren't Linux, e.g. macOS, where static linking is unsupported. I assume that Nim does not statically link in such cases instead of building a fragile executable.
The text was updated successfully, but these errors were encountered: