-
Notifications
You must be signed in to change notification settings - Fork 7
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
Attempt to build wkdev-sdk for multiple target platforms #16
Conversation
FWIW I was just waiting for Github Actions to have public ARM runners. Otherwise I've been using it on my ARM laptop already. |
7ede69b
to
8598fc2
Compare
I've been toying locally with qemu-user-static + podman build --platform support, and it works just fine out of the box.
Great to hear! |
32fa14a
to
cc1087b
Compare
Sounds great! |
cc1087b
to
b3d525b
Compare
b3d525b
to
2c025a6
Compare
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.
We still need the build to consistently succeed, but all sounds good to me.
Podman allows to build multi-architecture OCI images, that combine e.g. amd64 images + arm64 + ... in one image. Combined with qemu, one can easily build images for foreign architectures from amd64 hosts. Use that to extend wkdev-sdk to 'linux/arm/v7', besides the existing 'linux/amd64' support. Extend the GitHub workflow to produce multi-architecture images. Let's see where this goes :-)
2c025a6
to
900ae22
Compare
This fails in the cross-arch builds unfortunately.
900ae22
to
287aa71
Compare
I believe this next build will pass 🤞 But the fact this goes from 40 minutes to 3 hours sucks... I'd like to move it to a matrix to parallelize it. It is possible to create a manifest that points to other images so it won't appear any different even if deployed separate. |
This ended up getting reverted as the deploy step didn't work.
|
Still WIP.