-
Notifications
You must be signed in to change notification settings - Fork 15.5k
Add Windows release binary builds #150793
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
base: main
Are you sure you want to change the base?
Conversation
|
I was finally able to get the script working with help from @zmodem to debug some of the issues. Right now this is x86 only. It may be possible to add aarch64, but we would need to change the build script to reduce the build time in order to fit under the 6 hour timeout. |
zmodem
left a comment
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.
Very nice!
Not an expert on the environment that this runs in, but from what I can tell, LGTM.
boomanaiden154
left a comment
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.
Some minor comments, broadly LGTM.
| - name: Collect Variables | ||
| id: vars | ||
| env: | ||
| LLVM_VERSION_FROM_SOURCE: ${{ format('{0}.{1}.{2}', steps.version-from-source.outputs.major, steps.version-from-source.outputs.minor, steps.version-from-source.outputs.patch) }} |
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.
Might be worth it in a future refactoring to make this an explicit output from the composite workflow.
| "X64" ) | ||
| tar_arch="x86_64" | ||
| ;; | ||
| "ARM64" ) |
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.
Is there a reason we need to explicitly handle Windows on ARM given we do not support it currently? Just making things easier in the future?
| artifact-id: ${{ steps.artifact-upload.outputs.artifact-id }} | ||
| steps: | ||
| # It's good practice to use setup-python, but this is also required on macos-14 | ||
| # due to https://github.com/actions/runner-images/issues/10385 |
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.
Old comment given this should be Windows specific?
| # due to https://github.com/actions/runner-images/issues/10385 | ||
| - uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 # v6.1.0 | ||
| with: | ||
| python-version: '3.9' |
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.
Why python 3.9 over something newer?
No description provided.