annotate PLUGIN_HOWTO @ 14612:1f46715c08d9

[gaim-migrate @ 17340] Put gaim-text and the gnt stuff into a gaim-text RPM so that our main RPM doesn't depend on ncurses. rpmbuild -ta gaim-2.0.0dev.tar.bz2 doesn't work for me anymore. Did it used to? Does it work for other people? For me it prints error: Name field must be present in package: (main package) error: Version field must be present in package: (main package) error: Release field must be present in package: (main package) error: Summary field must be present in package: (main package) error: Group field must be present in package: (main package) error: License field must be present in package: (main package) And it creates a file called "tar: Pattern matching characters used in file n ames. Please," in my ~/rpmbuild/SPECS directory. It does not put gaim.spec in my ~/rpmbuild/SPECS directory, and it does not put anything in ~/rpmbuild/BUILD or ~/rpmbuild/SOURCES, either committer: Tailor Script <[e-mail]>

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.