Create workflow for Windows x64 builds #638
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! I'm not sure why the clippy tests are failing now and not before, but I've opened #639 to fix it. Rebasing after that should in theory fix the CI failures. |
FreezyLemon
force-pushed
the
ci-win-build
branch
from
5dacd09 to
ab7b5c7
Compare
redzic
approved these changes
Jun 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting point for #530.
Builds an x64 executable and uploads it as a workflow artifact (example run)
The exact workflow trigger is still open for discussion. And maybe there's some way to automatically add the artifact to a release? Haven't looked into it yet, this is just the build.
Dependencies:
Cargo packages are also cached. NASM could also be cached, but I didn't see it as a high priority.
Happy to hear your thoughts