-
Notifications
You must be signed in to change notification settings - Fork 41
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
Build support for multiple architectures #110
Conversation
Codecov Report
@@ Coverage Diff @@
## master #110 +/- ##
=======================================
Coverage 98.14% 98.14%
=======================================
Files 3 3
Lines 54 54
=======================================
Hits 53 53
Misses 1 1 Continue to review full report at Codecov.
|
[ch7059] |
…d undefined values.
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.
Thanks @mlxd! This is really cool!
Have left a few comments, mainly for my understanding/learning.
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.
Thanks @mlxd for the comments! Approved 💯
Context: This PR enables wheel-building for previously unsupported hardware architectures.
Description of the Change: Wheel-build support is added for the following hardware architectures:
(ppc64le)
, ARM64(aarch64)
(arm64)
The wheel-builder actions have also been separated to more easily allow selective building per PR created. This is partly due to the parsing order of the Github Actions YAML, where job
if
statements are evaluated before any matrix statements, introducing skipped tests with undefined potentially overlapping labels.All x86_64 wheel build operations are run for each PR created. For Linux
ppc64le
andaarch64
, and MacOSarm64
these are built only when a PR is merged with master, due to the additional overheads required.Benefits: This will simplify installation and use on the above platforms.
Possible Drawbacks: Additional efforts may be required to keep build-system up-to-date with any modifications or changes. Additional cluttering of workflows directory due to lack of support for nested Actions directories.