linuxdeployqt VS AppImageLauncher

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.

Every file that you want to execute has to be in your environment PATH. I would also advise to put symlinks and personal executables in ~/.local/bin and put that to your path. Since your user has ownership over that directory, you won't have any probs with permissions that may or may not occur at all. Since we're talking about AppImage files, you might also want to take a look at AppImageLauncher which does a pretty good job at creating entries for your Desktop Menu for the AppImage files that you install to your system.

I think it's safe to install it directly as it stores everything in a single directory. For AppImages there is also AppImagePool + AppImageLauncher (can be installed rootless, useful for better integration of appimages).

This reminds me of a prettier version of AppImageLauncher. Is there also an "Uninstall" option in the right-click menu of the app launcher?

I'm using AppImageLauncher on Fedora.

"... I recall that this was related to an issue with most Electron apps, wherein the AppImage cannot be integrated with the desktop or the favourites bar. So far we've found that the AppImageLauncher (https://github.com/TheAssassin/AppImageLauncher) helps with getting around this!