Mercurial > pidgin
view PLUGIN_HOWTO @ 14618:2f0b4d0de5bb
[gaim-migrate @ 17346]
Fix the argument GaimValue types in a handful of signal registrations. These
being wrong didn't matter to things that knew/guessed what their arguments
were (i.e. C functions) but did matter to things that needed to trust the
GaimValue type information for the types (i.e plugin loaders). I'm pretty sure
I got this all right, it matches the docs at least.
I still think there are a couple problems (namely the *-timestamp functions
returning a GAIM_TYPE_POINTER instead of a GAIM_TYPE_STRING) but these were
much more obvious.
committer: Tailor Script <tailor@pidgin.im>
author | Etan Reisner <pidgin@unreliablesource.net> |
---|---|
date | Mon, 25 Sep 2006 06:01:12 +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.