Package Details: qolibri 1.0.4-2

Git Clone URL: https://aur.archlinux.org/qolibri.git (read-only)
Package Base: qolibri
Description: A QT-based EPWING dictionary viewer
Upstream URL: http://qolibri.sourceforge.jp/
Licenses: GPL2
Submitter: None
Maintainer: None
Last Packager: 2ion
Votes: 2
Popularity: 0.000295
First Submitted: 2011-08-12 11:36
Last Updated: 2015-06-08 18:51

Latest Comments

2ion commented on 2015-03-15 13:31

I have submitted a fixed PKGBUILD with corrected qt4 package name and build command. The application still builds without error that way.

2ion commented on 2015-03-08 18:17

The code is Qt4 only. Seems like you were about to use qt5.2.

diffycat commented on 2014-01-12 13:38

Can't build that one. With qt4 as dependency I got:

==> Starting build()...
Project MESSAGE: Version = 5.2.0
Project MESSAGE: Translations = /usr/share/qt/translations
Project MESSAGE: Config = lex yacc debug exceptions depend_includepath testcase_targets import_plugins import_qpa_plugin qt warn_on release link_prl incremental gdb_dwarf_index shared qpa no_mocdepend release qt_no_framework linux unix posix gcc
Project MESSAGE: Plugins =
Project MESSAGE: Defines =
Project MESSAGE: Libs = -leb
Project MESSAGE: Include Path = src
Project MESSAGE: Installs = target i18n i18n_s
Project MESSAGE: Target = qolibri
g++ -c -pipe -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -Wall -W -D_REENTRANT -fPIE -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib/qt/mkspecs/linux-g++ -I. -Isrc -I/usr/include/qt -I/usr/include/qt/QtGui -I/usr/include/qt/QtCore -Ibuild -o build/qolibri.o src/qolibri.cpp
src/qolibri.cpp:25:24: fatal error: QApplication: No such file or directory
#include <QApplication>
^
compilation terminated.
Makefile:647: recipe for target 'build/qolibri.o' failed
make: *** [build/qolibri.o] Error 1
==> ERROR: A failure occurred in build().
Aborting...

Anonymous comment on 2011-08-12 11:41

If anyone actually uses this instead of EBView, sorry for ending up doing the install manually in the PKGBUILD. The software author had hardcoded in paths so the package wouldn't play nice with makepkg, and I couldn't be bothered to start patching that.