Extend Github action to cross-compile to aarch64/arm/i686 for Linux #98
Conversation
StephanvanSchaik
force-pushed
the
cross-compile
branch
from
a7e0060
to
cde0a6e
Compare
StephanvanSchaik
changed the title
| - name: Run tests | ||
| run: cargo test --target ${{ matrix.target.rust }} | ||
| - name: Doc | ||
| run: cargo doc --target ${{ matrix.target.rust }} |
There was a problem hiding this comment.
Another option, if you want, is to use actions-rs/cargo with the use-cross option enabled. That makes the whole thing easier, and you don't have to install the dependencies or anything, and you only have to use the rust target triple in the matrix.
There was a problem hiding this comment.
Honestly, I don't know. I have looked at cross in the past and while it does look more convenient, I don't like its dependency on Docker/Podman at all.
This instead reflects my actual workflow which is to use rustup to install a Rust toolchain for the specific target, run the cargo commands with the specified target, and then run it in using QEMU userspace emulation for that target, which I agree is more involved, but at the same time I know what is going on exactly.
Also, I simply have more experience with QEMU userspace emulation, because I have used that for things outside of Rust like preparing a Linux image for AArch64 using chroot.
Maybe it offers better performance for Github CI? I am not sure, as at the end of the day I am not too familiar with cross, but that could be a good reason to use it for Github CI.
|
Can we have a 0.12.1 in the meantime that can properly compile again? Not sure if there's a better issue to post this in. |
|
I see no reason to hold this back. If it causes problems we can revert it. |
Extend the Github workflow to set up QEMU and the Rust toolchain, and then build/test evdev for various targets (aarch64, arm and i686).
This way we can also easily catch issues like #95 and #96 and also #82.