Skip to content

CI: the windows cross build installs the one mingw target it uses #237

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.

Sign up for GitHub

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

Merged
closer-claudio merged 1 commit into from
Nov 10, 2026
Merged

CI: the windows cross build installs the one mingw target it uses #237

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/scripts/build-erofs-utils.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,14 @@ build_windows() {
[ "$(uname -s)" = "Linux" ] || die "the windows cross-build needs a linux host"
if [ -z "${SKIP_DEPS:-}" ]; then
apt_get update
apt_get install -y autoconf automake libtool pkg-config mingw-w64
# Not the mingw-w64 metapackage: it pulls both targets (i686 and
# x86_64), both thread models (posix and win32) and g++, 277 MB in 25
# packages, which the mirror has served at a package a minute, past
# the guard, on three runs out of three. The cross build is C on one
# target with one thread model: the compiler, its binutils and the
# headers for x86_64 alone, a quarter of that.
apt_get install -y --no-install-recommends autoconf automake libtool pkg-config \
binutils-mingw-w64-x86-64 gcc-mingw-w64-x86-64-posix mingw-w64-x86-64-dev
fi
mkdir -p "$work"

Expand Down
Loading