Running on ARM
Instructions for running on ARM-based hardware such as PinePhone, Raspberry Pie etc:
Run using ./gradlew run locally as described in https://code.briarproject.org/briar/briar-desktop#building-and-running
or build a architecture-specific jar: ./gradlew packageUberJarForCurrentOS.
If the software crashes, enable software rendering (how to do that?)
Activity
added Document label
marked this issue as related to #325
Note: this article has info on how to enable software rendering which might fix crashes on some fixes. Although, the article also mentions that Compose for Desktop will automatically fall back to software rendering when Skiko is not able to create a hardware-accelerated context. But who knows, maybe on some systems that check causes a crash already, so enabling software rendering manually might help and even help diagnosing causes of problems.
-
As pointed out by @akwizgran in case of problems to run on ARM, it might prove useful to check which version of libc is in use on that system. In the past there were problems with getting ARM-32 binaries to work. Some issues involved floating point abi stuff, which hopefully is no longer an issue on ARM-64.
Also keep in mind that some systems don't even feature the "default" libc library but some other standard library. One example is PostmarketOS which I documented (alongside a loooot of other ARM systems) in briar#1854 (closed):
Ah, seems that pmOS uses musl libc rather than glibc:
https://wiki.postmarketos.org/wiki/About_postmarketOS
-
I have a Raspberry Pie 4 Model B which has an ARM64 processor and now that I've also ordered an SD card and HDMI adapter, I was actually able to try it. I installed Raspbian which apparently is a Debian-based OS optimized for the Raspberry Pie. It has a desktop environment based on LXDE. I was able to run the nightly build on it without major issues. I get this error message about libnotify having some problem (I'll post the exact message later), but the app starts and runs smoothly. Notifications do not work and are not detected to be not working (which might be the thing that we could ideally detect). I think it's not much our fault though. After installing
x11-utils, I havenotify-sendwhich also doesn't work. It fails silently, much like our app. I think there's just nothing installed on that system that shows the notifications that are being sent to libnotify. 
This sounds like a problem unrelated to our ARM building, so probably worth a separate issue?
Also: Is this a duplicate of #454 (closed) ?
mentioned in merge request !284 (merged)
mentioned in issue #516
-
Fixed via !284 (merged)