-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
binary size is scary #140
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
Comments
I don't think there's a whole lot we can do. I mean, we could strip unneeded symbols after compilation, but that doesn't really solve the problem (the binaries would still be huge). IMO, the best we can hope for is the Rust compiler eventually generating smaller binaries. |
This is 100% a compiler & standard library issue; the smallest one can get a statically linked executable that uses Work-arounds include:
|
On the current version of the project, most binaries end up between 271kB - 471kB (stripping on, LTO off due to this bug). Is there a need to make this any smaller? rustc 1.4.0-nightly (63ba780fd 2015-08-23) |
What about shipping a standard library for OS not having rust library and using dynamic linking ? |
see the issue above for more details on this issue, dynamic linking. |
I like the busybox idea. |
duplicated #747 |
I know its a rust issue, but looking at about 3MB for each binary, versus around 100KB for coreutils binaries on my system (ubuntu 14.04), I wonder if there is anything that can be done to cut it down.
The text was updated successfully, but these errors were encountered: