4 ms·
I find the number for xargo, without stripping or UPX to be by far the most interesting. It almost gets you all the way (1/6th of the default release size), whi
by arghwhat 9y ago
I find the number for xargo, without stripping or UPX to be by far the most interesting. It almost gets you all the way (1/6th of the default release size), while not breaking anything.
Stripping removes useful things from your binary, and UPX tends to be a no-go for many things.
- steveklabnik 9y agoWe've been talking about "unforking xargo", and treating libstd/etc more like any other crate, which would mean that you could do this in a more easy way. It's gonna take some time though.
- nixpulvis 9y agoThis sounds like a really good idea! Would there still be prebuilt versions for the sake of faster builds out of the box?
- steveklabnik 9y agoI haven’t been following the exact details, but that would make sense.
- kibwen 9y agoDetails are still up in the air. All we know for sure (decided at the Rust All-Hands last week) is that we definitely want to extend cargo in a way that obviates xargo (a plan which xargo's maintainer has enthusiastically endorsed).
- JoshTriplett 9y agoBased on the discussions in the Rust All-Hands last week: yes, there will still be pre-built versions of std for common platforms.