Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 21125:23d046a20aa0
Improved cyrus sasl support on win32:
- Actually install the cyrus sasl libraries and plugins
- Add INSTDIR/sasl2 to sasl plugin path at runtime so cyrus can
find the mechanisms
- Remove cyrus sasl bits during uninstallation
(installation is still conditional on CYRUS_SASL=1 being defined)
author | Stu Tomlinson <stu@nosnilmot.com> |
---|---|
date | Sat, 03 Nov 2007 20:13:51 +0000 |
parents | c6e563dfaa7a |
children | 48d09d62912e |
line wrap: on
line source
#define DBUS_API_SUBJECT_TO_CHANGE #include <stdio.h> #include <stdlib.h> #include "purple-client.h" /* This example demonstrates how to use libpurple-client to communicate with purple. The names and signatures of functions provided by libpurple-client are the same as those in purple. However, all structures (such as PurpleAccount) are opaque, that is, you can only use pointer to them. In fact, these pointers DO NOT actually point to anything, they are just integer identifiers of assigned to these structures by purple. So NEVER try to dereference these pointers. Integer ids as disguised as pointers to provide type checking and prevent mistakes such as passing an id of PurpleAccount when an id of PurpleBuddy is expected. According to glib manual, this technique is portable. */ int main (int argc, char **argv) { GList *alist, *node; purple_init(); alist = purple_accounts_get_all(); for (node = alist; node != NULL; node = node->next) { PurpleAccount *account = (PurpleAccount*) node->data; char *name = purple_account_get_username(account); g_print("Name: %s\n", name); g_free(name); } g_list_free(alist); return 0; }