Hi. AppImage is a way to distribute software as a single file. Inside the appimage there's a compressed filesystem, which contains not only the executeable, but also all libraries and resource files needed. At runtime, this filesystem gets mounted under /tmp. Your binary might be at /tmp/.mount12345/usr/bin/camotics, with some files at /tmp/.mount12345/usr/share/camotics, and others at /tmp/.mount12345/usr/share/doc/camotics. I made a camotics appimage but unfortunately, camotics keeps looking for files in /usr/share/ , defeating the purpose of an appimage.
I've been looking at how prusa-slicer handles this. prusa-slicer looks for a resource directory relative to its binary, like this: (in PrusaSlicer.cpp)
Hi. AppImage is a way to distribute software as a single file. Inside the appimage there's a compressed filesystem, which contains not only the executeable, but also all libraries and resource files needed. At runtime, this filesystem gets mounted under /tmp. Your binary might be at /tmp/.mount12345/usr/bin/camotics, with some files at /tmp/.mount12345/usr/share/camotics, and others at /tmp/.mount12345/usr/share/doc/camotics. I made a camotics appimage but unfortunately, camotics keeps looking for files in /usr/share/ , defeating the purpose of an appimage.
I've been looking at how prusa-slicer handles this. prusa-slicer looks for a resource directory relative to its binary, like this: (in PrusaSlicer.cpp)
Just FYI.