Mercurial > pidgin
diff PLUGIN_HOWTO @ 15944:1071320641b9
merge of '7e96b2a5202c1dd624ba497a2713aec816233996'
and 'ac156097f694ba8977900a053e669e480c15e274'
author | Sadrul Habib Chowdhury <imadil@gmail.com> |
---|---|
date | Tue, 27 Mar 2007 01:38:37 +0000 |
parents | cc3c50816cc9 |
children | 83ec0b408926 |
line wrap: on
line diff
--- a/PLUGIN_HOWTO Tue Mar 27 01:36:24 2007 +0000 +++ b/PLUGIN_HOWTO Tue Mar 27 01:38:37 2007 +0000 @@ -1,20 +1,7 @@ -For information on writing a plugin for Gaim, go -http://gaim.sourceforge.net/api/ and see the HOWTOs in the -"Related Pages" section. +For information on writing a plugin for Purple, Pidgin or Finch, go +http://pidgin.im/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 +doxygen and graphviz dot, then running "make docs" in the 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.