Skip to content
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

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

Open
Serpentarius13 opened this issue Sep 7, 2024 · 3 comments

Comments

@Serpentarius13
Copy link

Serpentarius13 commented Sep 7, 2024

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

@ahrm
Copy link
Owner

ahrm commented Sep 8, 2024

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
Copy link
Owner

ahrm commented Sep 11, 2024

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

@hrdl-github
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants