view README.dbus @ 12600:e856f985a0b9

[gaim-migrate @ 14934] Enable the extra warnings regardless of --enable-debug. Enable FORTIFY_SOURCE regardless of --enable-debug, adding a --disable-fortify flag to configure. Enable (well, stop disabling) the missing initializer warnings. This leads to warnings with: GValue v = {0,}; that must be worked around. Basically, instead of: GValue v = {0,}; ... g_value_init(&v, G_TYPE_FOO); /* or other use of the GValue */ We'd need to do: GValue v; ... v.g_type = 0; g_value_init(&v, G_TYPE_FOO); /* or other use of the GValue */ Fix several cases of missing initializers. I don't think any of these are bugs, but having this warning seems like a good idea. It might prevent us from making a mistake in the future. While I was fixing missing initializers, I optimized substitute_simple_word in plugins/spellchk.c, in the same way as I did substitute_word before. Yes, I'm bad for committing these together. Added a --enable-fatal-asserts flag to configure. As the name implies, this makes g_return_... guards fatal. This is a useful flag to run on a debug copy of Gaim. It will make it very clear if your changes have triggered one of these guards. It's also useful in detecting g_return_... abuse, which helps prevent crashes if Gaim is compiled with G_DISABLE_ASSERT defined. 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.