1Purple, Pidgin and Finch
3See AUTHORS and COPYRIGHT for the list of contributors.
5libpurple is a library intended to be used by programmers seeking
6to write an IM client that connects to many IM networks. It supports
7AIM, ICQ, XMPP, MSN and Yahoo!, among others.
9Pidgin is a graphical IM client written in C which uses the GTK+
12Finch is a text-based IM client written in C which uses the ncurses
15These programs are not endorsed by, nor affiliated with, AOL nor any
16other company in any way.
21Read the 'INSTALL' file for more detailed directions.
23These programs use the standard ./configure ; make. You need to use
24gmake, BSD make probably won't work. Remember, run ./configure --help
25to see what build options are available.
27In order to compile Pidgin you need to have GTK+ 2.0 installed (as
28well as the development files!). The configure script will fail if you
29don't. If you don't have GTK+ 2.0 installed, you should install it
30using your distribution's package management tools.
32For sound support, you also need gstreamer 0.10 or higher.
33Your distro of choice probably already includes these, just be sure to
34install the development packages.
39You should run 'make install' as root to make sure plugins and other files
40get installed into locations they want to be in. Once you've done that,
41you only need to run 'pidgin' or 'finch'.
43To get started, simply add a new account.
45If you come across a bug, please report it at: https://developer.pidgin.im
50If you do not wish to enable the plugin support within Purple, run the
51./configure script with the --disable-plugins option and recompile your
52source code. This will prevent the ability to load plugins.
54'make install' puts the plugins in $PREFIX/lib/purple (PREFIX being what
55you specified when you ./configure'd - it defaults to /usr/local). Purple
56looks for the plugins in that directory by default. Plugins can be installed
57per-user in ~/.purple/plugins as well. Pidgin and Finch also look in
58$PREFIX/lib/pidgin and $PREFIX/lib/finch for UI-specific, respectively.
60To build a plugin from a .c file, put it in the plugins/ directory in
61the source and run 'make filename.so', e.g. if you have the .c file
62'kickass.c', put it in the plugins/ directory, and from that directory,
63run 'make kickass.so'.