-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
dist: Ship more Windows import libs with the rust-mingw package of *-windows-gnullvm targets.
#151108
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
base: main
Are you sure you want to change the base?
dist: Ship more Windows import libs with the rust-mingw package of *-windows-gnullvm targets.
#151108
Conversation
…`*-windows-gnullvm` targets. This fixes building crates like https://crates.io/crates/blake3, which use `cc` and depend on additional Windows import libs. The list of shipped Windows import libs now matches the `rust-mingw` package of the `x86_64-pc-windows-gnu` target.
|
rustbot has assigned @Mark-Simulacrum. Use |
| "libmingw32.a", | ||
| "libmingwex.a", | ||
| "libmsvcrt.a", | ||
| // Windows import libs, remove them once std transitions to raw-dylib |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct me if I'm wrong, but if I understand this correctly, the list of import libraries is supposed to be exactly those that are necessary for the standard library. Once the standard library uses raw-dylib all import libraries would be removed from the rust-mingw package.
If you got a crate which uses cc, doesn't that mean you also have to have a Mingw C toolchain installed separately anyway? That toolchain should contain all import libraries C code may need.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct me if I'm wrong, but if I understand this correctly, the list of import libraries is supposed to be exactly those that are necessary for the standard library. Once the standard library uses raw-dylib all import libraries would be removed from the rust-mingw package.
This is correct, even for regular windows-gnu targets rust-mingw is not meant to provide full toolchain. Even less so when it comes to windows-gnullvm.
If you got a crate which uses cc, doesn't that mean you also have to have a Mingw C toolchain installed separately anyway? That toolchain should contain all import libraries C code may need.
BLAKE3 can build without C compiler, but in "degraded" mode - without optimised assembly. The problem here is usage of page_size crate, which depends on winapi. It's abandoned and shouldn't be used for years. This should be easy to solve in BLAKE3 repo.
|
r? @mati865 (or feel free to suggest someone else with more familiarity with this list) |
This fixes building crates like https://crates.io/crates/blake3, which use
ccand depend on additional Windows import libs.The list of shipped Windows import libs now matches the
rust-mingwpackage of thex86_64-pc-windows-gnutarget.Addendum to #147536
CC @mati865