Mercurial > pidgin
view PLUGIN_HOWTO @ 15592:0a5823d45398
Fix a few small compile warnings:
gtkblist.c: In function ¡Æpidgin_blist_paint_tip¡Ç:
gtkblist.c:2352: warning: suggest explicit braces to avoid ambiguous ¡Æelse¡Ç
gtkblist.c:2370: warning: suggest explicit braces to avoid ambiguous ¡Æelse¡Ç
gtklog.c: In function ¡Æpidgin_log_show_contact¡Ç:
gtklog.c:699: warning: ISO C90 forbids mixed declarations and code
gtkstatusbox.c: In function ¡Æadd_popular_statuses¡Ç:
gtkstatusbox.c:842: warning: unused variable ¡Æheight¡Ç
gtkstatusbox.c:842: warning: unused variable ¡Æwidth¡Ç
gtkstatusbox.c:841: warning: unused variable ¡Æemblem¡Ç
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Fri, 09 Feb 2007 07:34:51 +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.