From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [RFC] Building Signal-Desktop (and other electron applications) on aarch64
Date: Sun, 23 Oct 2022 05:57:38 +0200 [thread overview]
Message-ID: <20221023035738.OkD1ALaycKwSsKFcIGl7XxlkdkZBUs4OSJ1AwFapNc0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38609@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Closed issue by akierig on void-packages repository
https://github.com/void-linux/void-packages/issues/38609
Description:
I'm looking for help figuring out how to natively build Signal-Desktop (and potentially other Electron applications) on `aarch64`. As noted in my most recent update to Signal-Desktop (PR #38565) they are packaging a native version for Apple Silicon, but my own attempts to recreate their build using an Apple Silicon based Mac have been unsuccessful.
However there is a third-party [build for `aarch64`](https://elagost.com/flatpak/) that is provided through flatpak.[^1] I was able to get it running under a Debian ARM VM. Though Flatpak has a variety of issues that make it undesirable as a long term solution.
I'd welcome any help or PRs to get this working for ARM. I don't presently have a Void ARM VM setup, so anyone who'd be willing to try building it on either a VM or bare metal would be appreciated.
Note: I'm not a JS/Node Developer and have approximately zero desire to be one, no disrespect to those who are. I only maintain Signal-Desktop because I use it extensively.
[^1]: see also: https://gitlab.com/elagost/signal-desktop-builder
next prev parent reply other threads:[~2022-10-23 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 13:59 [ISSUE] " akierig
2022-10-23 3:57 ` akierig [this message]
2022-10-23 3:57 ` [ISSUE] [CLOSED] " akierig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221023035738.OkD1ALaycKwSsKFcIGl7XxlkdkZBUs4OSJ1AwFapNc0@z \
--to=akierig@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).