Skip to content

Release: Windows takes NASM 2.16.03, never Chocolatey's newest - #148

Merged
shinyobjectz merged 1 commit into
mainfrom
win-nasm-pin
Nov 13, 2026
Merged

shinyobjectz merged 1 commit into
mainfrom
win-nasm-pin

Conversation

@shinyobjectz

@shinyobjectz shinyobjectz commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

rc4's Windows build (run 43493625589) failed at raea.exe's link: 135 of openh264-sys2's SIMD routines unresolved (WelsSampleSad16x8_sse2 and the rest), though its C++ was compiled to call them. That run took Chocolatey's NASM; GitHub's image, where rc3 linked, has 2.16. The nasm step now always unpacks NASM's own 2.16.03 zip, puts it first on PATH and fails if nasm -v names another version.

Mac and Linux built warm on Namespace in this run: 36 min and 7 min (183 and 105 on GitHub's runners).

…ocolatey's newest

rc4 on Namespace's Windows image installed Chocolatey's NASM, and raea.exe failed to link: 135 of openh264's
SIMD routines (WelsSampleSad16x8_sse2 and the rest) unresolved, though openh264's C++ was built to call them.
GitHub's image, where rc3 linked, ships NASM 2.16. The step now always unpacks the 2.16.03 zip, puts it first
on PATH and fails if nasm -v names another version.
@shinyobjectz
shinyobjectz merged commit cbd7649 into main Nov 13, 2026
4 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