-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add macOS arm64 support #19193
base: master
Are you sure you want to change the base?
Add macOS arm64 support #19193
Conversation
Co-authored-by: Pythyu <Pythyu@users.noreply.github.com>
Changes in |
# Packages which must be built from source | ||
always_build=() | ||
|
||
if false && [[ "${DD_BUILD_PYTHON_VERSION}" == "3" ]]; then |
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.
Disabled the rebuild of confluent-kafka
and librdkafka
because some module doesn't support universal2 wheels and I didn't managed to force take the arm64 wheel instead of universal
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.
I don't think it is necessary for macOS m1 to have kerberos
support at least for now since the main goal is to allow easier local building on our laptops
@@ -320,6 +327,7 @@ jobs: | |||
- name: Create pull request | |||
uses: peter-evans/create-pull-request@v5 | |||
with: | |||
base: pythyu/macos_arm_build |
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.
Hack I used to get .deps
inside of this branch. Will be removed when merging
What does this PR do?
Add support to build arm64 macOS integrations, most of it is taken from original x64 macOS files and adapted for arm64
Motivation
Used on my hackathon project
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged