I'm running debian on aarch64.
Just tried to create an appImage for "dragon" (a video player).
I can see it from the script logs that it uses x86_64 while creating appImage:
Running AppImageTool...
appimagetool, continuous build (commit 90704a0), build <local dev build> built on 2022-09-14 18:51:26 UTC
Using architecture x86_64
/home/pi/projects/arch2appimage/AppDir should be packaged as out/dragon-aarch64.AppImage
Deleting pre-existing .DirIcon
Creating .DirIcon symlink based on information from desktop file
Generating squashfs...
Parallel mksquashfs: Using 6 processors
Creating 4.0 filesystem on out/dragon-aarch64.AppImage, block size 131072.
... and as a result, the appImage it creates is not functioning:
pi@orangepi4-lts:~/projects/arch2appimage/out $ ./dragon-aarch64.AppImage
/tmp/.mount_dragon7MZCvM/AppRun: 14: exec: dragon: Exec format error
I think if the Arch binary package is not compliant to current system architecture the script should make a full stop and give that kind of detail to user.
I'm running debian on aarch64. Just tried to create an appImage for "dragon" (a video player). I can see it from the script logs that it uses x86_64 while creating appImage:
... and as a result, the appImage it creates is not functioning:
I think if the Arch binary package is not compliant to current system architecture the script should make a full stop and give that kind of detail to user.