mc as AppImage #4943
-
|
Maybe someone has any positive experience packaging mc into an AppImage? I tried with appimage-builder1 and with build-appimage-action, and while everything seems OK, the resulting AppImage fails to use some of the included files. For instance, I can get this when launching: While if I extract the AppImage, all the mentioned resources would be present in the squashfs-root folder. My understanding is that for some reason, despite the fact that the AppImage creation process actually packs those files into the resulting AppImage, mc, when launched from it, looks for them outside, in the host machine's folders (doesn't find them and reports the failure). In other words, I'm under impression that I'm maybe missing some options or some steps in my yml-recipe that would force mc to look inside the AppImage for these resources? Any hints would be more than welcome :) Footnotes
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
appimages require the builds to be relocatable. this is fundamentally opposite to traditional unix deployment processes, which is nicely illustrated by the fact that to this day there is no standardized way to obtain the path of the current executable. the qt toolkit abstracts over that, but has a limited range of supported platforms. i didn't find a glib equivalent. |
Beta Was this translation helpful? Give feedback.
-
|
Check this out: Lines 98 to 114 in 885426a |
Beta Was this translation helpful? Give feedback.
Check this out:
https://appimage-builder.readthedocs.io/en/latest/examples/gimp_path_mapping.html
https://source.midnight-commander.org/man/mc.html#FILES
mc/src/main.c
Lines 98 to 114 in 885426a