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
Currently we only support the following platforms on the Release Binaries pipeline:
aarch64-apple-darwin: MacOS Apple Silicon (M1+M2)
x86_64-apple-darwin: MacOS x86-64
x86_64-linux-gnu: Linux x86-64
As described in #684, it is also desirable to support ARM SoCs and SBCs.
The two most popular architectures being:
aarch64-unknown-linux-gnu
arm-unknown-linux-gnueabi
I started working on this a while ago by proposing a shell script via PR #684, but since we have a binary release pipeline, it makes more sense add support for these targets via release-bin.yaml instead, without adding any additional shell script.
It is a Github Action that allows cross-compilation of Rust projects via cargo cross.
While working on this issue, the contributor should make some mock releases on their fork as a way to validate that the workflow is behaving as expected.
The text was updated successfully, but these errors were encountered:
Currently we only support the following platforms on the
Release Binaries
pipeline:aarch64-apple-darwin
: MacOS Apple Silicon (M1+M2)x86_64-apple-darwin
: MacOS x86-64x86_64-linux-gnu
: Linux x86-64As described in #684, it is also desirable to support ARM SoCs and SBCs.
The two most popular architectures being:
aarch64-unknown-linux-gnu
arm-unknown-linux-gnueabi
I started working on this a while ago by proposing a shell script via PR #684, but since we have a binary release pipeline, it makes more sense add support for these targets via
release-bin.yaml
instead, without adding any additional shell script.This could also be useful: https://github.com/houseabsolute/actions-rust-cross
It is a Github Action that allows cross-compilation of Rust projects via cargo cross.
While working on this issue, the contributor should make some mock releases on their fork as a way to validate that the workflow is behaving as expected.
The text was updated successfully, but these errors were encountered: