Hi, So mupdf upstreams says "fitz is still immature and should not be exposed nor dynamically linked" (#719351). But isn't the point of zathura-mupdf to encapsulate mupdf within a .so plugin and maintain a stable interface between this plugin and zathura? That should not be a blocker.
Zathura upstream seems very actively maintaining the plugin (last release a week ago) and surely they will be friendly to work with over this issue. And because actually Zathura proper and the zathura-mupdf plugin are by the same author, it would be ridiculous if the two don't work together. Therefore I propose to pull in libmupdf.a to build the zathura-mupdf shared library. Right now to build the pdf.so of zathura-mupdf, just - apt-get source mupdf - HAVE_MUJS := no in there - rebuild libmupdf-dev with DEB_BUILD_OPTIONS=x-fpic - dpkg -i libmupdf-dev...deb - cd zathura-mupdf; remove "-lmujs" there - make - zathura --plugins-dir=zathura-mupdf test.pdf And it renders lightning fast!!! -Lingzhu -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CACnaKDRUzAMzbET5JkmMGXd7=s6tsr_1hxaaa1un5cl99k8...@mail.gmail.com
