do not assume a build's purpose based on its target architecture

[brjsp]

commit be737c3 removes some features on linux aarch64 (and only aarch64), i'm assuming because they are only used by the electron app.

I maintain the signal-desktop package in openSUSE. in addition to x86_64, we also provide aarch64, armhf and riscv64 versions. We'd like to keep the application fully-functional across all architectures.

If you need to build a version of ringrtc with some functionality disabled in your CI, please cleanly delineate it as a cargo feature instead of making such assumptions.

[mutexlox-signal]

The problem that be737c3 is trying to fix is that we have a dep that was failing to build on aarch64 linux (see mozilla/cubeb-rs#97).

This is a short-term workaround to avoid breaking the build until that dep is fixed and the fix is pushed to crates.io; we do want to build this feature for aarch64 linux once that's done.

[mutexlox-signal]

BTW, thanks for your work on maintaining the package for openSUSE :)