deezer-linux icon indicating copy to clipboard operation
deezer-linux copied to clipboard

Any chance for Arm64 / aarch64?

Open mitchweaver opened this issue 2 years ago • 8 comments

Title

With Asahi Linux becoming popular / usable would be nice to package for aarch64

mitchweaver avatar May 21 '23 22:05 mitchweaver

Hi, for flatpak I don't know how to build for arm, but if you want a hand-made solution you can build from source: make install_deps And then:

yarn --cwd run build-deb-arm

Which yields you an artifact in artifacts; you can change it to build snap, appimage, rpm, ... instead (see https://github.com/aunetx/deezer-linux/blob/master/package-append.json)

If this works for you, I will see about automatizing this an producing artifacts for both arm and amd64!

aunetx avatar Jun 21 '23 17:06 aunetx

@mitchweaver I added aarch64 support, and I plan to push it to flathub too BUT I can't test it myself (as I only have an amd64 laptop).

Could you test it from the latest version (you can use the package you prefer, even appimage -- I just want to know if it works)?

aunetx avatar Jul 08 '23 16:07 aunetx

@aunetx Sorry been a while missed this, looks like it does not

mitch@macbook[tmp] ./deezer-desktop-5.30.580-arm64.AppImage
Segmentation fault

mitch@macbook[tmp] cd deezer-desktop-5.30.580-arm64
mitch@macbook[deezer-desktop-5.30.580-arm64] ./deezer-desktop
Segmentation fault

mitch@macbook[deezer-desktop-5.30.580-arm64] uname -a
Linux macbook 6.4.11-401.asahi.fc38.aarch64+16k #1 SMP PREEMPT_DYNAMIC Mon Aug 21 19:38:10 UTC 2023 aarch64 GNU/Linux

mitchweaver avatar Aug 30 '23 04:08 mitchweaver

I'm sorry, I don't have any way to test it on arm... If someone wants to check what is wrong, I'm very open to PRs :)

aunetx avatar Sep 25 '23 10:09 aunetx

Hi everyone, is this maybe related to this: https://github.com/refi64/zypak/issues/25

This is fixed in recent Chromium versions, included in Electron 19 and 18.3.7+. Any apps just need to upgrade their Electron versions to work, unfortunately.

What version of Electron is currently used? Is it "electron": "^13.6.9", which is set in package-append.json?

jnlmmln avatar Dec 14 '23 07:12 jnlmmln

@jnlmmln yes, it is electron 13 that is used. I am trying right now to upgrade to electron 28 (after all, it might work!), but if it is too high I will find a good version to work with.

aunetx avatar Dec 27 '23 16:12 aunetx

I can't get anything higher than electron 13 to work to be honest...

aunetx avatar Dec 27 '23 16:12 aunetx

I am no expert here, but is it possible to not package the electron13 within the same package, but configure it as a dependency instead?

I tried running it on my Raspberry Pi, which is also ARM64 based, and I got the same segmentation fault. Obviously it's not working with an x86 binary.

eduarddejong avatar Mar 31 '24 15:03 eduarddejong