comparison plugins/HOWTO @ 144:e8dae982b37c

[gaim-migrate @ 154] I figured I should document how to make your plugin configurable and how to compile it (even though compiling it should be pretty obvious from reading the Makefile). committer: Tailor Script <tailor@pidgin.im>
author Eric Warmenhoven <eric@warmenhoven.org>
date Fri, 21 Apr 2000 00:03:52 +0000
parents c2d22261e281
children be408b41c172
comparison
equal deleted inserted replaced
143:01be71085964 144:e8dae982b37c
40 J. Random Hacker also has the same name on a global variable, you won't be 40 J. Random Hacker also has the same name on a global variable, you won't be
41 constantly overwriting each others' variables. Unfortunately, this also means 41 constantly overwriting each others' variables. Unfortunately, this also means
42 that plugins will have difficulty working together. But then again, that's 42 that plugins will have difficulty working together. But then again, that's
43 what shared memory is for. 43 what shared memory is for.
44 44
45 Plugins can be configured. This makes is so they don't have to be recompiled
46 in order to change things internal to them, and it's also just a cool feature
47 to have :). It's optional; to allow your plugin to be configured, add a
48 function called gaim_plugin_config(). The advised course of action is to have
49 it pop up a dialog window; but it's your plugin.
50
45 When your plugin gets unloaded, gaim will try to call gaim_plugin_remove(). It 51 When your plugin gets unloaded, gaim will try to call gaim_plugin_remove(). It
46 doesn't have to be there, but it's nice if, say, you create a window, and when 52 doesn't have to be there, but it's nice if, say, you create a window, and when
47 the plugin gets unloaded, it removes the window. Also, all the callbacks you 53 the plugin gets unloaded, it removes the window. Also, all the callbacks you
48 have attached to gaim signals will be removed. 54 have attached to gaim signals will be removed.
49 55
56 Compilation of the plugins is fairly straight-forward; there is a Makefile in
57 this directory that has a rule for making the .so file from a .c file. No
58 modification of the Makefile should be necessary, unless if you simply want
59 to type 'make' to have it made; otherwise, 'make filename.so' will take
60 filename.c and make the .so plugin from it.
61
50 There are a few examples in this directory. Enjoy. 62 There are a few examples in this directory. Enjoy.