-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Ship static binaries #4589
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
Duplicate of #4354; see there and in the linked PR for why this is not possible currently. |
NixOS should actually work fine after #4555. |
Woosh, that was fast. Thanks! Though #4555 is only about VSCode, right? What about coc-rust-analyzer? |
@fannheyward by the way, it's not very clear to me how the two extensions differ and whether it's likely for them to diverge even more or converge back. |
|
I would like to use
rust-analyzer
. However, most ways of obtaining it require one to use a downloaded version, which I guess is build againstx86_64-unknown-linux-gnu
. This hurts the portability as these binaries will not work on distros like Alpine Linux or NixOS (at least without further ).I would appreciate if the binaries will be build against the
x86_64-unknown-linux-musl
target in the future in order to achieve maximum compatibility. IMHO it is always wrong to ship a dynamic linked binary if static linkage is an easy option but if one exactly knows the target system (which is not the case if one binary is provided for the whole linux world).Other than that, thank you all for the great work!
PS: For me
rust-analyzer
compiles againstx86_64-unknown-linux-musl
just fine, so this shouldn't be fairly quick fix.The text was updated successfully, but these errors were encountered: