sioyek icon indicating copy to clipboard operation
sioyek copied to clipboard

sioyek: error while loading shared libraries: libmupdf.so.24.8: cannot open shared object file: No such file or directory

Open Serpentarius13 opened this issue 1 year ago • 3 comments

Hey! This error is happening when trying to use either sioyek or sioyek-git repos. Only `sioyek-appimage' works on Arch, but it seems very outdated. I think detailed guide on how to manage build results to folders (like where to put bin + shaders + configs) is needed, so it would be manageable to build package myself since package managers versions are handled by other people, I was very confused when building myself as not-so-knowledgeable user. This would help other distros too

Serpentarius13 avatar Sep 07 '24 23:09 Serpentarius13

My suggestion is that you build with linux_app_image qmake config (qmake "CONFIG+=linux_app_image"). It doesn't actually build an appimage but produces a binary that can be converted to appimage. This config uses the mupdf 1.22 which is included in the source directory and the location of shader and config files are just next to the sioyek binary.

ahrm avatar Sep 08 '24 08:09 ahrm

I have updated the mupdf in the development branch to 1.24.

ahrm avatar Sep 11 '24 11:09 ahrm

I usually update sioyek-git on AUR when libmupdf is updated, triggering a recompilation and reinstallation using most AUR helpers. Otherwise you need makepkg -C reinstall sioyek-git yourself.

hrdl-github avatar Oct 20 '24 15:10 hrdl-github