Skip to content

Release: Linux arm64 + Windows 32-bit builds fail #63

Description

@oesukam

Two targets in the Release workflow matrix fail to build and are excluded from v0.1.0 (the other 7 targets ship fine, and latest.json correctly omits them).

1. Linux aarch64 (arm64) — cross-compile setup missing

Command "yarn tauri build --target aarch64-unknown-linux-gnu" failed with exit code 1
... PKG_CONFIG environment variable [not set]

Building the arm64 Linux target on an x86_64 runner needs the aarch64 cross toolchain and pkg-config pointed at an arm64 sysroot (webkit2gtk / gtk / etc.). The workflow doesn't provision this, so the build has never succeeded.

Options:

  • Add gcc-aarch64-linux-gnu + the arm64 webkit2gtk/libgtk dev packages (via dpkg --add-architecture arm64) and set PKG_CONFIG_PATH / PKG_CONFIG_SYSROOT_DIR / PKG_CONFIG_ALLOW_CROSS=1 before tauri build; or
  • Build arm64 on a native ubuntu-24.04-arm runner instead of cross-compiling.

2. Windows i686 (32-bit) — build fails

The Build (Windows x86 (32-bit)) job fails in the Build & upload step for the i686-pc-windows-msvc target. 32-bit Windows is a niche target; the x64 and ARM64 Windows builds both succeed.

Options:

  • Investigate the i686 build/signing failure; or
  • Drop 32-bit Windows from the matrix if it's not a supported target.

Scope

Neither blocks releases — the failed jobs just make the overall Release run red and skip the "Publish" / "Homebrew tap" convenience steps (which is why v0.1.0 was published manually from the draft). Fixing or dropping these two makes future Release runs green end-to-end.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions