view README.dbus @ 11719:109ee3bfeac5

[gaim-migrate @ 14010] SF Patch #1333770 from corfe83 "Many times in gaim we use the function g_slist_remove(list,node->data) to remove an element from a GSList. If we already have the pointer to the node we want to delete, it is faster to send it the pointer to the node to delete rather than the data of the node (we can do this by calling g_slist_delete_link(list,node)). This change was made while looking at glib's documentation and the code in glib's gslist.c. This is because as the remove/delete function traverses each node in the list, it doesn't need to spend an extra memory access to retrieve the data for each element in the node it is traversing and then compare, it can simply compare the pointer. In my tests outside of gaim, this makes a big difference if the node you are deleting is at a high index in the list. However, even if you're deleting the first node, it about breaks even. So, I've found each case in gaim where we are calling g_slist_remove, and we already have the pointer to the appropriate node to delete (this is often the case when we're doing a for or while loop on a GSList). I've then replaced it with the appropriate call to g_slist_delete_link. I, however, didn't do this in situations where we are explicitly removing the first element in the list, because in those situations it is an unnecessary change. There should be no difference in behavior, but just in case I've tried running it with valgrind, which reports the same number of memory leaks after my patch as before my patch. Of course, I can't guarantee that my normal behavior on gaim is hitting all the functions I've changed, but in general testing it Works For Me (tm)." As with the last patch, this one may not have a practical performance impact (or maybe it does, I have no idea), but it's not worse for any case. Given two ways of doing things where one is always at least as fast and may be faster under some cases, I like to prefer that faster way. This doesn't make the code any uglier, so I'm applying. committer: Tailor Script <[e-mail]>

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.