Tips on developing KRunner plug-ins (with Qt Creator?)

[Giacomo Alzetta]

No, I dont, see the last line in mytestrunner.cpp:
https://github.com/Bakuriu/MyTestRunner/blob/master/mytestrunner.cpp#L64

And this is exactly the thing that puzzles me. If I put the .desktop file
in place but I do not provide the .so library, I can see the KRunner load
stating that it is unable to find the plug-in. When the .so library is in
place no logging is produced to know whether it succesfully loaded the
plugin or not, and the plugin isn't called when matching nor is listed in
the configuration options.

that other file is automatically created by QtCreator, i just left it there
but I know it's not required.

Il giorno dom 10 lug 2016 alle ore 19:45 David Edmundson <
david at davidedmundson.co.uk> ha scritto:

>
> ​You're missing this line somewhere:
>
> K_EXPORT_PLASMA_RUNNER(my-test-runner, MyTestRunner)
>
> It exports the big that make it a plugin, with the entry point that
> krunner needs.
>
> Also you can then kill your mytestrunner_global.h code, as that's
> exporting code for linking against, which is a bit different.
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160710/6645507b/attachment.html>