-
Notifications
You must be signed in to change notification settings - Fork 57
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
Incompatibility when dynamically linking libappimageupdate in GTK app #211
Comments
libappimageupdate does not use Gtk+, I can't imagine this is related to our project in any way. Also, static linking is not a recommended strategy. |
@Seren541 can you post a link to the AppImage in question please? How do you create it? If it ships any Gtk platform plugin themes for Qt, then these should be removed, similar to #152. |
This should then be discussed elsewhere. Also, it is unclear whether the application in question uses Qt at all. |
I think I have the same error. My AppImageUpdate.AppImage has exec permissions but double-clicking it does nothing, so I tried launching it from the terminal and I get some GTK errors:
Running Ubuntu 20.04.5 LTS. Please let me know if I can add some more information. Also, as an user of AppImages, I would prefer I could update AppImages, add .desktop files and icons from one single tool. |
The binary I am trying to build is this one: https://github.com/gholmann16/Neptune It will be difficult to build in your system because I have not as of yet made a portable build system due to the fact that I cannot even build it on my own yet. The issue is as follows. Gtk being available on most linux distros is leading me to dynamically link it. But libappimageupdate, being available nowhere is leading me to link it statically. When I make install and call the so file's functions, everything goes according to plan. But as soon as I statically link it (as well as all the dependencies generated by the makefile), it starts to have pixbuf issues, aka icons are not loading. I just tried it now roughly a year later and I get the exact same result. This is gtk3 for the record. |
After persuing the gerror returned this error is spammed: I think this is because gtk is linked to libz and libzsync is using a custom libz which is thereby not loading the correct libz for gtk? When I try to get rid of the libzsync2_libz.a file I get errors because this custom static build has custom symbols not found in the shared library, so now I'm at a loss basically. |
I had already fixed this once by
and in linuxdeploy/linuxdeploy-plugin-qt#109, so this sounds like a regression @TheAssassin? |
Your fix is to just remove gtk? My project is coded in gtk, not qt with gtk plugins so this is not really an option. |
I was assuming that the problematic application is AppImageUpdate, which is a Qt application and not a Gtk application. The fix is to remove Gtk theming for Qt from the AppDir. The fix to that issue was what I was referring to; but I understand now that you are trying to link AppImageUpdate from a Gtk application. I have no clue about that, sorry. It's probably not a good idea to link together Qt and Gtk in the same application anyway. So better just let the AppImageUpdate application handle the updating of your AppImage. |
For now I'll probably end up using the shared library as that works but I might end up going that route. |
When I dynamically link to libappimageupdate, I face no error, but when I try to statically link to libappimageupdate.a, I get this warning:
I cannot find any more specifics than this because I cannot remove the dependencies, which appimageupdate needs, but I have tried to see if other libraries are doing it and it seems to narrow down to libappimageupdate. I face the same problem both on Ubuntu and Arch Linux.
The text was updated successfully, but these errors were encountered: