Skip to content

fix: add zlib to SPC_WINDOWS_LIBS; drop win32-arm64 target#148

Merged
jasdeepkhalsa merged 1 commit intomasterfrom
feature/fix-win-release-3
Mar 7, 2026
Merged

fix: add zlib to SPC_WINDOWS_LIBS; drop win32-arm64 target#148
jasdeepkhalsa merged 1 commit intomasterfrom
feature/fix-win-release-3

Conversation

@jasdeepkhalsa
Copy link
Copy Markdown
Member

win32-x64: linker fails with 14 unresolved zlib symbols (compress, uncompress, deflate, inflate, gzdopen, etc.) because zlib is in SPC_EXTENSIONS but not SPC_WINDOWS_LIBS. On Windows there is no system zlib, so it must be listed explicitly for SPC to download and link zlib_a.lib. Fix: prepend zlib to SPC_WINDOWS_LIBS.

win32-arm64: SPC v2.8.2 hard-codes phpsdk-vs17-x64.bat, which passes 'x64_amd64' to vcvarsall.bat — an invalid argument on an ARM64 host (valid are amd64_arm64 etc.). It also always downloads the postgresql-16-windows-x64-binaries.zip regardless of runner arch. These are upstream SPC bugs; drop the target from the matrix and the publish step until SPC gains proper Windows ARM64 support. The npm package @dbdiff/cli-win32-arm64 skeleton is kept in place so arm64 Windows users get a clean 'Could not locate binary' error rather than an npm install failure.

win32-x64: linker fails with 14 unresolved zlib symbols (compress,
uncompress, deflate, inflate, gzdopen, etc.) because zlib is in
SPC_EXTENSIONS but not SPC_WINDOWS_LIBS. On Windows there is no
system zlib, so it must be listed explicitly for SPC to download
and link zlib_a.lib. Fix: prepend zlib to SPC_WINDOWS_LIBS.

win32-arm64: SPC v2.8.2 hard-codes phpsdk-vs17-x64.bat, which
passes 'x64_amd64' to vcvarsall.bat — an invalid argument on an
ARM64 host (valid are amd64_arm64 etc.). It also always downloads
the postgresql-16-windows-x64-binaries.zip regardless of runner
arch. These are upstream SPC bugs; drop the target from the matrix
and the publish step until SPC gains proper Windows ARM64 support.
The npm package @dbdiff/cli-win32-arm64 skeleton is kept in place
so arm64 Windows users get a clean 'Could not locate binary' error
rather than an npm install failure.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Mar 7, 2026

@jasdeepkhalsa jasdeepkhalsa merged commit 7c81303 into master Mar 7, 2026
57 checks passed
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