Mercurial > pidgin.yaz
view PLUGIN_HOWTO @ 16591:ce049678a67b
soname versioning of libpurple. Should help resolve debian bug 421282
All version control is within configure.ac now
Adjust the define for purple_version_suffix as appropriate:
[devel] - normal development periods
[betaN] - for beta releases
[] - for releases
Follow the instructions in configure.ac to set the version number depending on
how the API has changed (ie. following our normal version numbering!)
version.h is auto-generated now
Added purple_version_check(), purple_major_version, purple_minor_version,
& purple_micro_version for run-time version comparisons in addition to the
existing compile time macros.
libpurple Plugins moved again, this time to:
$(libdir)/purple-$PURPLE_MAJOR_VERSION
This will allow parallel installations of different major libpurple versions
in the future should someone wish to.
author | Stu Tomlinson <stu@nosnilmot.com> |
---|---|
date | Sat, 28 Apr 2007 16:55:31 +0000 |
parents | 83ec0b408926 |
children | db5a58aabe38 |
line wrap: on
line source
For information on writing a plugin for Purple, Pidgin or Finch, go http://developer.pidgin.im and click on API. From there, 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 source tree. The documentation will be in the docs/html directory.