Mercurial > pidgin.yaz
view PLUGIN_HOWTO @ 15005:5e07a6f8eb33
[gaim-migrate @ 17784]
SF Patch #1571670 from zdeqb
"Perl bindings for the functions in core.h and some
bindings for the functions in privacy.h."
I made the following changes:
1. I chose to export gaim_get_core() as Gaim::get_core instead of Gaim::Core::get_core.
2. I don't see any reason to require Perl code to pass bogus values just because C requires them. So, I changed Gaim::Core::quit_cb to NOT take an argument, and to pass NULL to gaim_core_quit_cb().
3. I fixed a typo.
4. I cleaned up some spacing issues.
I noticed that Core.c didn't get created from Core.xs until I re-ran configure. Maybe there's no way to avoid this?
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Sun, 19 Nov 2006 19:58:45 +0000 |
parents | 7acebc9d043f |
children | cc3c50816cc9 |
line wrap: on
line source
For information on writing a plugin for Gaim, go http://gaim.sourceforge.net/api/ and see the HOWTOs in the "Related Pages" section. You can also generate this documentation locally by installing doxygen and graphviz dot, then running "make docs" in the Gaim source tree. The documentation will be in the docs/html directory. This next paragraph is old and possibly out of date: Compilation of the plugins is fairly straight-forward; there is a Makefile in this directory that has a rule for making the .so file from a .c file. No modification of the Makefile should be necessary, unless if you simply want to type 'make' to have it made; otherwise, 'make filename.so' will take filename.c and make the .so plugin from it. If you need to link in with extra libraries, you can set the environment variable PLUGIN_LIBS to be the libraries you want to link with. It should be possible to compile plugins outside of the Gaim source tree, which is a much cleaner solution.