[Resolved] Why Rust standard library depends on development packages?
#1
Sun, 2017-05-21 00:14
Franklin Yu
-
- Offline
- 10 months 6 days ago
- 2017-03-12
Currently the package rust-stdlib depends on gcc, llvm-libunwind-dev, and musl-dev, which all seem to be development packages. I assume that typically package rust-stdlib is useful to run compiled Rust binary; to compile from source on Alpine Linux, rust or even cargo should be used instead. I expect rust-stdlib to depend only on llvm-libunwind and musl.
The package rust-stdlib is a development package, it is not necessary to run compiled Rust binaries, it is only necessary to compile them. The rust standard library is normally statically linked in and this package therefore contains only static libraries.
Then is there any package for Rust run-time library? What if I decide to dynamically link the Rust standard library?
No, as currently Rust does not have a defined or stable ABI. You can find more information about this in this issue: https://github.com/rust-lang/rfcs/issues/600
Thanks. I didn't know that Rust don't even have a defined ABI. I look forward to the stable ABI making a stand-alone Rust library possible.
I'll mark this as resolved, although it is actually deferred.