You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libappimage.so should probably be provided as a linker script that links the shared library together with the static library parts.
The file content would be: INPUT(libappimage.so.1.0 libappimage_hashlib.a libappimage_shared.a)
For libappimage.a I would to the same and copy/rename all the required static libraries that are used to link the shared library version:
Activity
TheAssassin commentedon Oct 31, 2025
What would be the advantage of this?
darealshinji commentedon Oct 31, 2025
Just an idea to make manual linking easier. Now that I think about it, a pkg-config script would probably do the same?
TheAssassin commentedon Oct 31, 2025
Isn't that something that would typically be solved in downstream packaging?
That said, contributions welcome!
darealshinji commentedon Nov 1, 2025
The .pc files for a library are normally created by the library's build system, typically from a template file: https://www.scivision.dev/cmake-generate-pkg-config/
edit: I see there is a .pc file already
https://github.com/AppImageCommunity/libappimage/blob/master/cmake/libappimage.pc.in
TheAssassin commentedon Nov 7, 2025
That file was contributed externally as well. Thus, contributions welcome.
darealshinji commentedon Nov 9, 2025
This should do the trick: