You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to figure this out as part of reviving the snap, however there were a few barriers which made this difficult.
Gtihub action runners are only x86_64 (no aarch64 machines).
Cross-compiling with snapcraft is not very straightforward or well supported. Most discussion on this points to snapcraft's build services that offer arm machines however these services have caveats that make them less than ideal.
I don't actually have any device to test the result with!
Here are the options I was able to research for potential methods to get arm64 builds working each of which has various caveats. Note, the premise is that we want to be able to automate when builds are produced in order to deliver security updates (that is updates of the dependencies built into the packaged snap) (and as a bonus this makes creating new releases easier).
No auto builds when security updates are needed (maybe we could setup something were a github action pushes to a branch when a new build is needed for security updates).
I'm not sure how much control is given for selecting what branch is published to.
I tried to figure this out as part of reviving the snap, however there were a few barriers which made this difficult.
Here are the options I was able to research for potential methods to get arm64 builds working each of which has various caveats. Note, the premise is that we want to be able to automate when builds are produced in order to deliver security updates (that is updates of the dependencies built into the packaged snap) (and as a bonus this makes creating new releases easier).
The text was updated successfully, but these errors were encountered: