Re:Rust 1.0: Scheduling the trains
by alkonaut on Friday December 12, 2014 @01:47PM
(#8741926)
That must be under something other than windows. Rust on Windows definitely still has issues with static linking, dependence on gcc libs for 32bit exception handling etc.
Being able to build smaller statically linked binaries on windows is hopefully a priority.
[ Parent
| on HN ]
Re:Rust 1.0: Scheduling the trains
by steveklabnik on Friday December 12, 2014 @02:07PM
(#8742044)
As I said before, a dependence on libgcc and glibc are expected. It's not an issue with static linking, you don't generally statically link those two dependencies.
Is that expected to ever change and/or does Rust expect to work with other libcs (bionic? musl-libc?) Being able to build completely self-contained static binaries can be very nice at times, and for embedded use, glibc is pretty large...
I thought Rust used llvm for compilation? That makes the libgcc dependency seem a bit odd. Maybe I misunderstood?
Re:Rust 1.0: Scheduling the trains
by steveklabnik on Friday December 12, 2014 @02:37PM
(#8742229)
Right now, it can't work with other libcs, but if you strip things down enough, it's not required to use glibc either, for example, if you're building an OS. You just end up throwing away a lot of the standard library. Check out stuff like http://zinc.rs/ for embedded Rust.
libgcc is used for stack unwinding, not for compilation. So it does seem a bit weird at first :)