Skip to content

Conversation

@davidanthoff
Copy link

I have no idea whether this will work, but maybe worth a try? I don't have a M1, so I can't even test this :)

But it does build something when I run the workflow on my fork, and the compiler log has output that suggests it is actually building an arm64 version. The upload step fails in my fork, and I am not familiar enough with that to fix this. Maybe a maintainer here could test things and see whether this might actually be producing the correct binaries?

@chearon
Copy link
Collaborator

chearon commented May 17, 2023

I don’t think it could be this easy because all of the dependencies have to be in the right architecture too.

@davidanthoff
Copy link
Author

Ah, true...

Is the most realistic option here to get a Mac mini, and add that as a self-hosted runner? At least until GitHub offers M-chip hosted runners? I have a downstream project that is very much stuck on the lack of prebuild M1 binaries here, and it might be the easiest for me to just get a Mac mini and (if you are ok with that) connect it to this repo here?

@antonio-iodice
Copy link

Any clue on how this could be picked up again? Is this something anyone can do?

@jamesbvaughan
Copy link

This should be possible now that GitHub offers Apple silicon runners, right?

https://github.blog/2023-10-02-introducing-the-new-apple-silicon-powered-m1-macos-larger-runner-for-github-actions/

@chearon
Copy link
Collaborator

chearon commented Dec 7, 2024

Merged @jamesbvaughan's PR, so this is obsolete. Thanks for the effort anyways!

@chearon chearon closed this Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants