Feature request: ARM build

[barnscott]

Feature request:
org.signal.Signal does not exist in the ARM remote. Arm build available in flathub would be appreciated.

[vasyugan]

Just want to second this. Now that the pinephone ships, an arch build would be greatly appreciated!

[yorambh]

It's not even possible to build this flatpak package to ARM "from source" because the "build" just collect and re-installs the binaries from deb package.
this is probably related to the vendor tying to prevent usage of other builds in there network. without getting into this argument, it should be legit to create a build-from-source apckage that will be available to more ARCHs

[yookoala]

Seems it's possible to cross-compile into ARM .deb from source: signalapp/Signal-Desktop#3410

[olof-nord]

It is possible, but with a large amount of hacks, as outlined by @lsfxz.

I would actually recommend looking up axolotl.
A flatpak is available but not yet merged to main.

[lsfxz]

I've been trying to get a wayland/ozone build working for the PinePhone as well, but it's honestly even more of a pain then just building "regular" signal desktop for aarch64 – I've built electron 8, 9 and 10 with ozone support and each version needed a trove of different "hacks" to build; some of them then didn't even run on the PinePhone, and with the latest signal didn't run. I've given up on it for now until (hopefully soon) wayland/ozone support lands in upstream electron and it all gets quite a bit less messy.

Soooo I'd support looking axolotl as @olof-nord has recommended – looks quite a bit more sane to me ;)

[yorambh]

is it likely to be a problem with Signal that a non "formal" client is used ? They did have a problem with modified versions at a time.

[surprized]

I've been trying to get a wayland/ozone build working for the PinePhone as well, but it's honestly even more of a pain then just building "regular" signal desktop for aarch64 – I've built electron 8, 9 and 10 with ozone support and each version needed a trove of different "hacks" to build; some of them then didn't even run on the PinePhone, and with the latest signal didn't run. I've given up on it for now until (hopefully soon) wayland/ozone support lands in upstream electron and it all gets quite a bit less messy.

Soooo I'd support looking axolotl as @olof-nord has recommended – looks quite a bit more sane to me ;)

On openSUSE we have Signal on our repos but it relies on an electron prebuilt for x86_64. Any improvements for ARM in general will help us a lot, so please let us know if you make things work out.
See signal-desktop for reference code.
I too support the idea behind Axolotl, rather prefer that in devices with constrained resources (often the case for Ubuntu Touch).

[ExTechOp]

With the Apple M1 hardware the importance of ARM architecture just gets enhanced. Please, can someone work on this?

[sallyhaj]

I switched to Rassbperry pi as a desktop, hope we can see aarch64 bit version of the app.

[janvlug]

See also issue #46.

[Tigerpanzer02]

Seems like there is some traffic again, as archlinux can offer it, see https://aur.archlinux.org/packages/signal-desktop-beta

[Tigerpanzer02]

Just want to add that this would be also beneficial for chromeos devices

[fancsali]

I'd love this to happen; in fact I am trying to get Signal working on an old ARMv7 Chromebook, now running Linux.

[janvlug]

I did not see any reference here to Elagost flatpak yet. I use that flatpak on my Librem 5 Linux phone to run Signal Desktop.

[ExTechOp]

I just wish Elagost didn't say "I no longer use Signal. Updates are untested and shipped automatically by CI. Want to take over for me?" 😼

[alexhaydock]

Has there been any new consideration of this recently? As I understand it, it requires moving to source builds rather than just shipping the unpacked .deb, but with the newly GA release of Asahi Linux, this is something that more users are going to be interested in I'm sure.