Skip to content
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

Apple Silicon artifacts #501

Closed
scholarsmate opened this issue Feb 6, 2023 · 4 comments · Fixed by #878
Closed

Apple Silicon artifacts #501

scholarsmate opened this issue Feb 6, 2023 · 4 comments · Fixed by #878
Assignees
Labels
build CI Continuous integration (CI) cross-platform github_actions Pull requests that update GitHub Actions code packaging
Milestone

Comments

@scholarsmate
Copy link
Member

This project builds and runs on Apple Silicon, but we don't have a release process for Apple Silicon artifacts. It appears that Apple Silicon support is on the GitHub roadmap for Q3 2023 (github/roadmap#528). It would he helpful to publish Apple Silicon releases sooner, if practical.

@scholarsmate scholarsmate added CI Continuous integration (CI) cross-platform build packaging github_actions Pull requests that update GitHub Actions code labels Feb 6, 2023
@scholarsmate scholarsmate added this to the v1.0.0 milestone Feb 6, 2023
@shanedell
Copy link
Collaborator

shanedell commented Feb 9, 2024

Looking here https://github.com/actions/runner-images/blob/main/images/macos/ I should be able to macos-13-arm64 or macos-14-arm64. I will start with macos-13-arm64. This OS will also be used to create the Linux arm64 image by using a docker container.

@shanedell
Copy link
Collaborator

So it looks like the labels are macos-13-xlarge and macos-14-xlarge. However, there are charges to use these runners. See https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates, its $0.16 per minute for the M1 runner. https://www.flyci.net/ also has runners available but these also cost money but their smallest option is $0.08 per minute. So I don't think these will be viable option as you can see here https://github.com/ctc-oss/omega-edit/actions/runs/7850559446, it states

Native build and test on macos-13-xlarge 🦙
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.

@shanedell
Copy link
Collaborator

Okay looks like macos-14 is an m1 and free. But we the latest free non m1 version is macos-13

@shanedell
Copy link
Collaborator

So I believe I can get a build for apple silicon going. However, there may not be support Linux ARM64 as the macos-14 runner is a VM I believe so docker or podman can't be used as they don't support nested virtualization.

shanedell added a commit that referenced this issue Feb 10, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 11, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
shanedell added a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
github-merge-queue bot pushed a commit that referenced this issue Feb 12, 2024
- macos-14 uses an M1 mac so it creates an arm64 library file.
- used docker to create the ubuntu-20.04 arm64 image.
  - took some hacking around to get working, would have worked easier if macos-14 could have been the base os.
  - but since macos-14 is a VM running on an M1, it doesn't allow nested virtualization.

Closes #501
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build CI Continuous integration (CI) cross-platform github_actions Pull requests that update GitHub Actions code packaging
Projects
Development

Successfully merging a pull request may close this issue.

2 participants