3 ms·
If you are building for an embedded board, you don't need to follow the defaults; you can enable the flag to dynamically link to Rust's standard library, and th
by cesarb 4y ago
If you are building for an embedded board, you don't need to follow the defaults; you can enable the flag to dynamically link to Rust's standard library, and the main disadvantage of doing so (that Rust's standard library doesn't have yet a stable ABI) is not an issue when you're always rebuilding everything.
- synergy20 4y agoit is more than that,in short,rust is not really designed for shared stdlib,yes you can hack it but it is untested and u are on your own
- cesarb 4y agoIt's hard to say "it's untested" when the rustc compiler itself is usually compiled with shared stdlib: $ ldd `which rustc` linux-vdso.so.1 librustc_driver-1ca4abb0311ec689.so => /lib64/librustc_driver-1ca4abb0311ec689.so libstd-f1d4d1a0beb2c43e.so => /lib64/libstd-f1d4d1a0beb2c43e.so libc.so.6 => /lib64/libc.so.6 [...]