-
Notifications
You must be signed in to change notification settings - Fork 16.3k
build: fix ffmpeg generation on Windows non-x64 #47768
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good; just need to put back the conditional to only run this on release.
@jkleinsc yes, i did that intentionally to test the fix and would have replaced it before merging - confirmed:
|
No Release Notes |
I have automatically backported this PR to "38-x-y", please check out #47844 |
I have automatically backported this PR to "35-x-y", please check out #47845 |
I have automatically backported this PR to "37-x-y", please check out #47846 |
I have automatically backported this PR to "36-x-y", please check out #47847 |
Description of Change
Closes #47766
Refs #45466
Fixes an issue where ffmpeg builds didn't get built correctly on Windows arm64 or ia32
It seems we didn't properly set
GN_EXTRA_ARGS
for those platforms - i went back and checked our old appveyor configs and it's there:so we need to add that back here.
Checklist
npm test
passesRelease Notes
Notes: none.