Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign up[3.8] bpo-33125: Add support for building and releasing Windows ARM64 packages #17480
Conversation
This comment has been minimized.
This comment has been minimized.
|
FTR I have two test (release) builds running:
No practical difference between the two, except that the first also (successfully) produces (but won't publish) an ARM64 build. And I haven't yet run both to completion, but I need to walk away now and leave them, so we'll find out later whether they break! |
This comment has been minimized.
This comment has been minimized.
|
The build was successful, the only thing that failed was testing the installer (because it conflicted with the install on the machine... Meanwhile, the build from the 3.8 pipeline failed because I haven't backported one of the fixes for unsigned builds. But I think it's probably just best to backport all of it. |
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.
zooba commentedDec 5, 2019
•
edited by bedevere-bot
Note that the support is not actually enabled yet, and so we won't be publishing these packages. However, for those who want to build it themselves (even by reusing the Azure Pipelines definition), it's now relatively easy to enable.
The backport is mainly required for the new command line arguments to PC/support, which are used by the build definitions in master (even when targeting 3.8).
https://bugs.python.org/issue33125