Fantastic, I now having a working Okular under Windows - version 1.0.0
using KDE frameworks 5.20.0. For some reason the plugin loader was
looking for a file called okularpart.dll instead of libokularpart.dll. I
haven't found the cause of this, but just made a work-around by renaming
the installed library.
So, where to from here - should I log a bug report?
Thanks again for the help.
Cheers,
Jonathan
On 05/03/16 03:39, Thomas Friedrichsmeier wrote:
Hi,
On Fri, 4 Mar 2016 14:21:02 +1100
Jonathan Schultz <[email protected]> wrote:
[...]
I could then build and install okular successfully, but still can't
run it as it fails to find/load the okularpart plugin. I did what I
could with gdb, and found that the call to d->loader->load() on line
184 of kpluginloader.cpp fails. But the debugger refused to step into
that function call, and at that point I gave up trying to work out
where it is failing.
Can anyone help me with another pointer?
no more than stabbing in the dark, but you may want to try
"Process Monitor" to find out where kpluginloader is looking for files
(see https://techbase.kde.org/Projects/KDE_on_Windows/Tools).
In a possibly related issue, I note that kate won't find its plugins
unless QT_PLUGIN_PATH is set (it is inside an emerge environment, but
makes deployment tricky).
Regards
Thomas
_______________________________________________
Kde-windows mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-windows
_______________________________________________
Kde-windows mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-windows
