-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppRun do not link binary specified by -e argument #250
Comments
Need a log. |
this is on Debian11 32 bit, but got same on Debian12 64bit:
|
Could you please post your |
the file pointed by -d option is this: is -e option overridden by desktop file Exec entry, a desired behaviour? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I copy 2 binaries in
AppDir/usr/bin
, then call linuxdeploy to package deps and generate AppImage.One of the 2 binaries is also passed as
-e
argument as main binary.I saw the generated AppDir/AppRun link the other binary.
The AppDir is as so before call linuxdeploy:
AppDir/usr/bin/xnedit
AppDir/usr/bin/xnc
The linuxdeploy command is:
$ linuxdeploy-x86_64.AppImage -e source/xnedit --appdir AppDir -i resources/desktop/xnedit.png -d resources/desktop/xnedit.desktop --output appimage
Linuxdeploy generate this link:
AppDir/AppRun -> AppDir/usr/bin/xnc
instead of this one:
AppDir/AppRun -> AppDir/usr/bin/xnedit
Copy only
xnc
and skipping copyxnedit
before call linuxdeploy, results the same.The bash script is visible in this commit:
unixwork/xnedit@06ba0ca
and is runt with:
$ resources/AppImage/makeAppDir.sh XNEdit source/xnedit resources/desktop Linux
The text was updated successfully, but these errors were encountered: