view README.dbus @ 14960:0c80979077cf

[gaim-migrate @ 17738] * Patch from Christopher "cuberoot" to fix the repeated, CPU-intensive call loop on url_fetch_recv_cb() which was discussed on gaim-devl with the subject "Yahoo (and maybe others): gaim_util_fetch_url_request() at 100% CPU until complete with repeated EAGAIN". He writes: "When read() returns 0, that means eof... period. Don't check errno, don't collect $200. The loop was caused by eof condition when errno had previously been EAGAIN/EWOULDBLOCK. The CPU-bound loop stopped when errno happened to be overwritten. I also believe trying to use some/part of an HTTP request on ETIMEDOUT to be a mistake so I removed it. Funny enough the read(2) manpage doesn't document ETIMEDOUT as a possible errno, but it is. (see tcp_timer.c and tcp_subr.c in src/sys/netinet)." This closes Adium Trac ticket #5685. * Added some passing-NULL-to-printf() safety which has been sitting around in this file locally for a while, waiting for a worthwhile commit to accompany. committer: Tailor Script <tailor@pidgin.im>
author Evan Schoenberg <evan.s@dreskin.net>
date Sat, 11 Nov 2006 20:29:35 +0000
parents 2eca9ed49469
children
line wrap: on
line source

This file describes how to compile and run gaim with dbus support.
Hopefully, most of the steps from point 3 will soon be automated.


1. Make sure you have the latest version (0.34) of the dbus library
   installed, including glib bindings.  

   http://www.freedesktop.org/Software/dbus


2. Compile gaim

   ./configure --enable-dbus
   make
   make install


3. Configure your dbus instalation for gaim

   A. Find your dbus session configuration file, usually

      /etc/dbus-1/session.conf

   B. In that file, find the <servicedir> section.  This section
      contains the directory that stores files describing services,
      usually

      /usr/share/dbus-1/services

   C. Copy src/dbus-gaim.service to that directory

   D. Edit the dbus-gaim.service file you've just copied, and replace
      the path in the "Exec=" line with the path to your gaim
      executable.


4. Start Session DBUS if you haven't done it already

   eval `dbus-launch --session`
   export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID

   These commands will set the two above shell variables.  These
   variables must be set before running any dbus-aware programs.

Start gaim as usual.  To communicate with it, use "gaim-send".  When
you execute gaim-send, the dbus system will automatically start a gaim
process if one is not running already.