Maybe we should symlink ld-linux into each directory that contains ELF executables (e.g., usr/bin inside the AppImage), or symlink/move it at least into the directory of the main application.
Complication: We are looking for different payload applications when invoked through differently named symlinks. Those payload applications might be at different paths in the AppImage.
Potential heuristic:
Check the PATH variable in the AppRun we generate, and put one such symlink into each of those directories from the PATH that exist in the AppImage. When launching a payload application, always launch it through the ld-linux that is in the same directory as the payload application.
appimagetool -s deploybreaks things likeqApp->applicationDirPath().https://github.com/Murmele/Gittyup/pull/579#issuecomment-1629547188 contains a potential solution.
Maybe we should symlink ld-linux into each directory that contains ELF executables (e.g.,
usr/bininside the AppImage), or symlink/move it at least into the directory of the main application.Complication: We are looking for different payload applications when invoked through differently named symlinks. Those payload applications might be at different paths in the AppImage.
Potential heuristic: Check the PATH variable in the AppRun we generate, and put one such symlink into each of those directories from the PATH that exist in the AppImage. When launching a payload application, always launch it through the ld-linux that is in the same directory as the payload application.