linuxdeployqt VS arch2appimage

The second reason is the "modularity" of Arch, why Debian packages all the dependences in many different packages? Because a developer can isolate a bug or exclude that package using the right patch. Arch tends to package everything together. That's why an AppImage of Chromium for me is about 140 MB from a Ubuntu base and 280-300 from an Arch-base... but at least this is an issue of both arch-deployer and arch2appimage... I think that by using linuxdeployqt would be better in this case (SPOILER, it requires the host system with an old GLIBC version, also Debian Bookwork is too new for it xD ).

Eagle uses 'linuxdeployqt' for cross-platform installations. Read about it HERE. There is a qt.conf file in the directory where the eagle executable is located. I am not sure exactly how to use it.

linuxdeployqt allow to automatically pack all shared library that we need on binary file into single AppImage file, although linuxdeployqt mainly to generate AppImage for Qt application but it can use for general application, more information on https://github.com/probonopd/linuxdeployqt.

For raspberry on the other hand is an entirely diferent story. I tried to use this: probonopd/linuxdeployqt but with no avail. The problem is that if i download the AppImage directly from the github account i cannot use it in the raspberry because it is not compiled for raspbian or i was told. So, i tried downloading directly the source code and compile it using the Qt Creator on the raspberry but also i am encountering several problems. When i try to build qt creator gives me this error: MakeFile:65: sub-QtWebEngineApplication-qmake_all] Error 3. Also, i am receiving Unkown module(s) Qt:webengine in the Qt Creator.

You are looking for the windows equivalent of Mac DMG format, or linux appimage https://github.com/probonopd/linuxdeployqt/ / Flatpak.

# Generated by linuxdeployqt # https://github.com/probonopd/linuxdeployqt/ [Paths] Prefix = ../ Plugins = plugins Imports = qml Qml2Imports = qml

I am trying to use linuxdeployqt to create an appimage.

Arch2AppImage is useless, just like my Arch-Deployer (Arch2AppImage is inspired by my project, see it's README), I've also created an "issue" on its repository to explain why I've abandoned it, see https://github.com/hanzala123/arch2appimage/issues/25 ).

I'm a creator of AppImage packages, the basis always used (and recommended) is to create them based on old distributions for compatibility reasons. With this solution I want to try to break that rule. Both my Arch-deployer and the better known arch2appimage failed at this (and were archived as a result).

less than two years ago I published a bash script that can that downloads a package from the Arch repository or from ChaoticAUR with all its dependences, and this was a big success for me on this community and on github. Later someone else, inspired by this project, have developed its own tool with a better code and easier to use (DT on YouTube did also a review on it, here). Everithing is great, I'm glad about all this, but... I stopped work on my repo more than 1 year ago (about december 2021) for a reason, the same that I think the developer of arch2appimage have understand later (and I said it into an issue, here), that's why its project have no more commits since 9 months. Arch-based AppImages are not a good idea, here are two reasons:

If you are in Arch, arch2appimage can easily make packages from Chaotic AUR.