Summary:
This only depended on okularpart due to the export header used in the
kcfgc file, so use a dedicated one for the mobile components that doesn't
export anything.
This enables disabling the part build for mobile-only builds such as
Android, and thus removing the need for some difficult dependencies
like KParts.
Reviewers: aacid
Reviewed By: aacid
Subscribers: aacid, okular-devel
Tags: #okular
Differential Revision: https://phabricator.kde.org/D19037
okularplugin target from mobile/components suffers from the same problem as okularpart in https://git.reviewboard.kde.org/r/125741/
But the cause is a bit different now. okularplugin uses settings.cpp generated by KConfig and its header declares Settings class with OKULARCORE_EXPORT. For okularplugin target this macro gets expanded to __declspec(dllimport) and it makes linker to look for Settings class symbols in okularcore.
Fix this by tricking VS that we are building okularcore target.
REVIEW: 125742
this is an initial port of the qml component set of okular to qtquick2
it's straightforward, except pageitem that right now is a qquickpainteditem, that works fine, but a bit slower than generating and uploading the textures by hand (that may be an eventual future port)
the okular active application is still missing, but the components can be used from anywhere in qml
REVIEW:121326
Will make it easier to make separate apps based on the core in the future
Note this will most probably break your settings if you are not running a very up to date kdelibs (4.9 or 4.10)
so be careful on updating
REVIEW: 104947
Volker Krause
Aleix Pol
Martin T. H. Sandsmark
Olivier CHURLAUD
Thomas Friedrichsmeier
Gleb Popov
Marco Martin
Montel Laurent
Patrick von Reth
Frederik Gladhorn
Bogdan Cristea