linuxdeploy VS linuxdeployqt

name: Build DeSmuME AppImage on: push: branches: [ master ] pull_request: branches: [ master ] jobs: build: name: Build DeSmuME AppImage runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v2 - name: Install libfuse2 and Qt dependencies run: | sudo apt-get update sudo apt-get -y install libfuse2 qtbase5-dev qtchooser - name: Install dependencies run: sudo apt update && sudo apt install meson libsdl2-dev libpcap-dev libgtk-3-dev libgtk2.0-dev autoconf libglu1-mesa-dev - name: Build DeSmuME run: | cd desmume/src/frontend/posix/ meson build ninja -C build - name: List Build Folder Contents run: | cd desmume/src/frontend/posix ls -la cd ./build ls -la - name: Find Executable run: | # Buscar el archivo ejecutable de manera recursiva en el directorio de construcción executable_path=$(find desmume/src/frontend -name "desmume" -type f -executable) # Verificar si se encontró el archivo ejecutable if [[ -n "$executable_path" ]]; then echo "Archivo ejecutable encontrado en la ruta: $executable_path" else echo "Archivo ejecutable no encontrado." exit 1 fi - name: Install linuxdeploy and plugins run: | wget https://github.com/linuxdeploy/linuxdeploy/releases/download/continuous/linuxdeploy-x86_64.AppImage wget https://github.com/linuxdeploy/linuxdeploy-plugin-qt/releases/download/continuous/linuxdeploy-plugin-qt-x86_64.AppImage chmod a+x linuxdeploy-x86_64.AppImage chmod a+x linuxdeploy-plugin-qt-x86_64.AppImage - name: Build AppImage run: | ./linuxdeploy-x86_64.AppImage --appdir AppDir --plugin qt --output appimage mkdir dist mv ./AppDir/*.AppImage dist/ - name: Upload AppImage artifact uses: actions/upload-artifact@v2 with: name: desmume-appimage path: ./dist/

Check out LinuxDeploy as an example of tooling for packing up a Linux application with all dependencies and shipping an artifact that is easy to run: https://github.com/linuxdeploy/linuxdeploy

I recommend moving away from linuxdeployqt, and use linuxdeploy (almost the same name, but without the "qt" at the end). It has a Qt plugin, and it's as easy to use. Check how a real world application is using it, and it's with Qt 6.

You can use linuxdeploy if you want an alternative to generating the AppDir and the AppImage.

This is how you would generally build linuxdeploy (or any cmake project, in general): $ git clone https://github.com/linuxdeploy/linuxdeploy $ cd linuxdeploy $ cmake --build BUILD_DIRECTORY Where BUILD_DIRECTORY is either a directory in source path (eg. build) or another directory somewhere else (incase you want to do out-of-tree building)

You can use AppImage for this. It's easy to generate one using linuxdeploy, but I've found that it's not so easy to generate a fully portable one, when the distributions are very different in library versions.

The maintainer of that tool is rather hostile about allowing it to run anywhere but an ancient version of Ubuntu. If supporting ancient distributions isn't a requirement the similarly named linuxdeploy is a good choice. https://github.com/linuxdeploy/linuxdeploy

With it being rooted you could use Linux Deploy (requires Busybox) & then the documentation seems pretty robust for AdGuard Home. Tricky part would be to figure out how to give the phone a static IP.

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.