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;
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 ...
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)
In reply to Re: Purple/Pidgin perl plugin load error
by zdeqb
in thread Purple/Pidgin perl plugin load error
by Crackers2
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |