-
Notifications
You must be signed in to change notification settings - Fork 506
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
any chance of a windows-*
crate release
#2557
Comments
Which crate specifically?
Last I checked it only worked in nightly. Has something changed? @mati865 |
I think it's about
There is no stable/beta upstream compiler yet. MSYS2 provides downstream (think of it like Linux distro providing Rust in its repo) stable |
I can publish a semver compatible release of |
That'd be great! This is an example of the workaround I've had to apply to get packages using windows-targets 0.48.0 to build on aarch64-pc-windows-gnullvm: msys2/MINGW-packages#17654. It's been copied around to quite a few packages now. |
In case that wasn't clear yet, EDIT: oops, I think it was already clear, sorry |
On the topic of "semver breaking", be aware the crate is still pre-release so the following applies:
|
|
Thanks all, I think that's exactly what was needed. MSYS2 ships an Unlike on |
@kennykerr any chance of a
windows-*
crate release for this too? This would have been picked up in 0.50.0, but it looks like y'all declined to bump the version of the other crates.Building packages which use
windows-targets
on MSYS2's version ofaarch64-pc-windows-gnullvm
is entirely broken by this bug, and the only alternative is to useaarch64-pc-windows-msvc
(which only works on Windows hosts).I haven't yet got to a point where I'm cross-compiling ARM64 binaries from a non-Windows host; but I'd strongly suspect it's broken there too when using a non-nightly build, using the MSVC toolchain isn't an option, and there's no
aarch64-pc-windows-gnu
like forx86_64
.It looks like this project's CI only builds
-gnullvm
with Rustnightly
, so entirely side-steps the issue.Originally posted by @micolous in #2515 (comment)
The text was updated successfully, but these errors were encountered: