Perl bindings to plasma
Aaron J. Seigo
aseigo at kde.org
Sun Dec 5 00:37:18 CET 2010
On Tuesday, November 16, 2010, Chris Burel wrote:
> I've come up with two workarounds so far. One is to use LD_PRELOAD to
> load libperl.so, which isn't really a solution, but it did work in my
> test. The other is to modify KPluginFactory to have the option of
> specifying load hints in the constructor, and then have plasma check
> for a key in the .desktop file to determine if the symbols from the
> plugin should be exported.
>
> Or maybe there's some other/better way for me to make sure that
> loading kperlpluginfactory will export the necessary symbols from
> libperl.so?
sorry not replying sooner; i was hoping someone else would speak up who knew
more about these things than i.
it sounds to me like the KPluginFactory extension may be a good approach. but
i'd suggest asking on kde-bindings and kde-core-devel to see if anyone else
there has input.
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20101204/487df3dd/attachment.sig
More information about the Plasma-devel
mailing list