Package Details: qpdfview-bzr 2070-1

Git Clone URL: https://aur.archlinux.org/qpdfview-bzr.git (read-only, click to copy)
Package Base: qpdfview-bzr
Description: A tabbed PDF viewer using the poppler library. (development version)
Upstream URL: https://launchpad.net/qpdfview
Licenses: GPL2
Conflicts: qpdfview
Submitter: adamreichold
Maintainer: adamreichold
Last Packager: adamreichold
Votes: 8
Popularity: 0.000006
First Submitted: 2012-02-07 20:39 (UTC)
Last Updated: 2018-05-06 13:58 (UTC)

Dependencies (11)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

adamreichold commented on 2014-05-04 08:37 (UTC)

Hello, I changed detection of MuPDF to use "/usr/lib/libmupdf.a" again and updated the Fitz plug-in to work with MuPDF version 1.4. Best regards, Adam.

adamreichold commented on 2014-04-06 08:06 (UTC)

Hello Stefan, thanks for the hint. I changed the test to check for libmupdf-js-none.a instead. (Concerning the current master version of MuPDF itself, qpdfview will probably not work with because of API changes to which I will adapt when a new version of MuPDF is released and I find out to reliably detect the library's version for backwards compatibility.) Best regards, Adam.

haawda commented on 2014-04-05 13:07 (UTC)

I think the test if [ -f /usr/lib/libmupdf.a ]; then local config="$config with_fitz" fi is not correct. If I have my mupdf-git package installed, which no longer provides /usr/lib/libmupdf-js-none.a (and there is no obviuos way to provide it), the builds fails at the ld-step, trying to link /usr/lib/libmupdf-js-none.a So maybe you should test in the PKGBUILD, if that file exists instead.

haawda commented on 2014-03-08 10:33 (UTC)

I tried revision 1479, and that works fine. Thanks for the very quick reply and fix.

adamreichold commented on 2014-03-08 08:59 (UTC)

Hello, there was indeed a stray dependency on OpenJPEG in the build system which form the MuPDF source code examples but which isn't actually necessary. I just committed trunk revision 1478 which removes it, please retry. Best regards, Adam. P.S.: I also upload a new source package adding the missing dependency on desktop-file-utils.

haawda commented on 2014-03-08 08:38 (UTC)

Hello, something is going wrong for me when it comes to the final linking step. g++ -c -pipe -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_PLUGIN -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib/qt/mkspecs/linux-g++ -I. -I/usr/include/qt -I/usr/include/qt/QtWidgets -I/usr/include/qt/QtGui -I/usr/include/qt/QtCore -Imoc-fitz -o objects-fitz/moc_model.o moc-fitz/moc_model.cpp rm -f libqpdfview_fitz.so g++ -Wl,-O1,--sort-common,--as-needed,-z,relro -Wl,-O1 -shared -o libqpdfview_fitz.so objects-fitz/fitzmodel.o objects-fitz/moc_model.o objects-fitz/moc_fitzmodel.o -lmupdf -lmupdf-js-none -lfreetype -ljbig2dec -lopenjp2 -ljpeg -lz -lm -lQt5Widgets -lQt5Gui -lQt5Core -lGL -lpthread /usr/bin/ld: cannot find -lopenjp2 collect2: Fehler: ld gab 1 als Ende-Status zurück Makefile.fitz-plugin:171: recipe for target 'libqpdfview_fitz.so' failed make[1]: *** [libqpdfview_fitz.so] Error 1 make[1]: Leaving directory '/home/haawda/paketierung/not_maintained_by_me/qpdfview-bzr/src/qpdfview' Makefile:97: recipe for target 'sub-fitz-plugin-pro-make_first-ordered' failed make: *** [sub-fitz-plugin-pro-make_first-ordered] Error 2 For an older build (revision 1428), namcap tells me that desktop-file-utils should be a dependency, but that should be unrelated.

adamreichold commented on 2014-02-08 17:43 (UTC)

Hello again, the problem with the usual way of handling optional dependencies is that IMHO they are geared towards binary distribution. In that case I would have all those dependencies as "makedepends" and the program would just fail to load the corresponding plug-in if the optional (runtime) dependency is missing. But since AUR is basically source distribution, I don't want to force people to install all these packages just for building qpdfview if they don't want the plug-ins anyway, hence the slight abuse of meta-data. If qpdfview will ever be in the community repository, this would of course change to shipping separate packages for the different plug-ins in binary form. Regards, Adam.

lahwaacz commented on 2014-02-08 17:27 (UTC)

Right, I missed that... Thanks for the quick update. I don't think there are any official guidelines on handling "optional build-time dependencies", you could ask on aur-general mailing list. Using "optdepends" suggests that qpdfview built without mupdf installed can gain extra functionality by installing mupdf. This would be confusing on a binary repo. Plus, mupdf should not be needed at all at runtime, if only the static library is required at build-time.

adamreichold commented on 2014-02-08 16:58 (UTC)

Hello lahwaacz, I think the problem is in the PKGBUILD checking for the package "poppler" instead of "poppler-qt5" to decide whether to build the Poppler plug-in. I'll upload an update package... Regards, Adam. P.S.: All dependencies in "optdepends" except for "mupdf" are definitely runtime dependencies. MuPDF ships a static library and hence would be an optional build-time dependency for which no better key exists AFAIK.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »