Skip to content

Pin the autotools host type on Windows - #59

Merged
fcjr merged 1 commit into
mainfrom
windows-autotools-host
Nov 17, 2026
Merged

fcjr merged 1 commit into
mainfrom
windows-autotools-host

Conversation

@fcjr

@fcjr fcjr commented Nov 17, 2026

Copy link
Copy Markdown
Owner

The 0.6.3 Windows desktop build failed: libirecovery's configure required libusb (run).

libirecovery picks its native Windows backend only when host_os matches mingw32*. config.guess reports x86_64-w64-mingw32 inside the MSYS2 MINGW64 shell, which is where the CLI release and CI build. release-app builds from PowerShell instead, where it reports x86_64-pc-mingw64 (x86_64-pc-msys in my VM). That environment fell through to libirecovery's libusb backend. It only worked while MSYS2 still shipped mingw-w64-x86_64-libusb. So until now the Windows desktop app quietly used a different backend from the CLI.

This passes --build/--host=x86_64-w64-mingw32 to every autotools configure on Windows, so all environments build the native backend, the one tested in #58.

Checked in the Windows VM from plain PowerShell with no MSYSTEM: libirecovery's configure detects x86_64-pc-msys without the flags and x86_64-w64-mingw32 with them. A full cold cargo build of this branch in that environment is running; I'll note the result here.

0.6.3 shipped everything except the Windows desktop installer, and latest.json has no Windows entry, so the app leaves Windows users on 0.6.2 until the next release.

config.guess reports x86_64-w64-mingw32 inside the MSYS2 MINGW64 shell
but x86_64-pc-mingw64 (or -pc-msys) from a plain Windows shell, which is
how the desktop release builds. libirecovery only picks its native
Windows backend for host_os mingw32*; anywhere else it requires libusb,
which MSYS2 no longer packages for MINGW64, so the 0.6.3 Windows desktop
build failed at libirecovery's configure. Before that, desktop builds
quietly used libirecovery's libusb backend while the CLI used the native
one. Pass --build/--host=x86_64-w64-mingw32 so every environment
configures the same way.
@fcjr
fcjr merged commit 88759b7 into main Nov 17, 2026
7 checks passed
@fcjr
fcjr deleted the windows-autotools-host branch November 17, 2026 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant