in reply to Purple/Pidgin perl plugin load error

This is a late reply... but...

If you do the following, there is no need to links against glib. (Order does matter)

use Glib;
use Purple;

[download]

To get around the purple_perl_callXS error, you have to use LD_PRELOAD='' (or link against purple-2/perl.so, libpurple.so)

LD_PRELOAD='libpurple.so /location/to/lib/purple-2/perl.so' perl -MGli
+b -MPurple ...

[download]

But loading libpurple this way is pointless, since the current perl glue only exists so that a plugin can be written in perl. To actually write a client in perl some more glue is required. I started working on that glue (and it seems to work for me), and posted it at this link (there is an example in the libpurple/plugins/perl/scripts/nullclient.pl file after patching)

Replies are listed 'Best First'.
Re^2: Purple/Pidgin perl plugin load error
by Crackers2 (Parson) on Jun 11, 2007 at 20:15 UTC

    Interesting. Indeed use'ing both Glib and Purple gets rid of the g_str_hash error, but as you say still throws the purple_perl_callXS error.

    Writing a plugin in perl is all I'm really looking for.

[reply]
[d/l]
[select]

      this page this page seems to contain everything that's needed to write one. (It's a little old,but is mostly accurate)

[reply]

        The latest version of that page is up at http://developer.pidgin.im/doxygen/dev/html/perl-howto.html I believe.

        Both of them still use Gaim instead of Purple though.

        Regardless, I've seen those pages before and tried the example plugin, but it's actually throwing pretty much the same errors already mentioned above. Which is why I started this thread in the first place :)

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom