Mercurial > pidgin.yaz
view PLUGIN_HOWTO @ 15539:7ae72b7c02b1
sf patch #1640011, from Celso Pinto
Patch for gaim.spec that fixes dependencies on SUSE
Add line breaks to Evan's NEWS entry
sf patch #1639901, from Saleem Abdulrasool
Fix the build failure of the Mono example dlls due to the
Mono API change
Show "(experimental)" next to the enable-mono option
when calling "./configure --help"
sf patch #1644019, from good ol' Ka-Hing Cheung
"fix compiling on gtk 2.4. xmppconsole.c is the culprit.
gtk_combo_box_get_active_text is defined in gtk 2.6 but not 2.4."
Sun apparently doesn't like when void functions return
the return value from another void function. For example:
void func1(void) {
printf("hi");
}
void func2(void) {
return func1(); /* this line causes a warning */
}
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Sun, 04 Feb 2007 08:46:24 +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.