-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Don't link build scripts dynamically #1960
Conversation
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+
And even if there was, build scripts are transient anyway. |
📌 Commit 2116f81 has been approved by |
⌛ Testing commit 2116f81 with merge 02b5bb9... |
💔 Test failed - cargo-win-msvc-32 |
That is such a weird build failure. However I am glad that dojob is doing its job of cleaning up all the zombies. |
There's no real reason to eagerly link build scripts dynamically as they're not going to benefit that much from dynamic linking. Most of the time they only have one dynamic dependency, libstd, and most other Rust programs don't link it dynamically so there's not really many space savings either.
2116f81
to
13d5094
Compare
There's no real reason to eagerly link build scripts dynamically as they're not going to benefit that much from dynamic linking. Most of the time they only have one dynamic dependency, libstd, and most other Rust programs don't link it dynamically so there's not really many space savings either.
☀️ Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
There's no real reason to eagerly link build scripts dynamically as they're not
going to benefit that much from dynamic linking. Most of the time they only have
one dynamic dependency, libstd, and most other Rust programs don't link it
dynamically so there's not really many space savings either.