Mercurial > pidgin
comparison PLUGIN_HOWTO @ 15934:cc3c50816cc9
More gaim->whatever isms
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 26 Mar 2007 05:42:33 +0000 |
parents | 7acebc9d043f |
children | 83ec0b408926 |
comparison
equal
deleted
inserted
replaced
15933:b449dc6b8a20 | 15934:cc3c50816cc9 |
---|---|
1 For information on writing a plugin for Gaim, go | 1 For information on writing a plugin for Purple, Pidgin or Finch, go |
2 http://gaim.sourceforge.net/api/ and see the HOWTOs in the | 2 http://pidgin.im/api/ and see the HOWTOs in the "Related Pages" |
3 "Related Pages" section. | 3 section. |
4 | 4 |
5 You can also generate this documentation locally by installing | 5 You can also generate this documentation locally by installing |
6 doxygen and graphviz dot, then running "make docs" in the Gaim | 6 doxygen and graphviz dot, then running "make docs" in the |
7 source tree. The documentation will be in the docs/html directory. | 7 source tree. The documentation will be in the docs/html directory. |
8 | |
9 This next paragraph is old and possibly out of date: | |
10 Compilation of the plugins is fairly straight-forward; there is a | |
11 Makefile in this directory that has a rule for making the .so file | |
12 from a .c file. No modification of the Makefile should be necessary, | |
13 unless if you simply want to type 'make' to have it made; otherwise, | |
14 'make filename.so' will take filename.c and make the .so plugin from | |
15 it. If you need to link in with extra libraries, you can set the | |
16 environment variable PLUGIN_LIBS to be the libraries you want to link | |
17 with. | |
18 | |
19 It should be possible to compile plugins outside of the Gaim source | |
20 tree, which is a much cleaner solution. |