1 Empathy is split in different processes:
2 - src/empathy: contact list, considered as the main UI
3 - src/empathy-chat: chat UI
4 - src/empathy-call: call UI
5 - src/empathy-accounts: UI to configure IM accounts
6 - src/empathy-debugger: debug tool
8 Each process can be run directly from source without having to be installed to
9 its prefix. You just have to define an appropriate environment using the
10 wrapper found in the tools/ directory.. For example:
11 ./tools/empathy-env ./src/empathy
13 The chat and call UI are automatically started by telepathy-mission-control
14 when receiving or requesting a chat/call. In order to use your custom version
15 you have to kill any existing instance of empathy-{chat,call} and then start
16 it with EMPATHY_PERSIST=1 to prevent it from auto exiting if there is no
17 channel to handle. For example:
18 EMPATHY_PERSIST=1 ./tools/empathy-env ./src/empathy-chat
20 Debugging can be turned on using EMPATHY_DEBUG=all and logged to a file
21 with EMPATHY_LOGFILE=/tmp/empathy.log
23 Sometimes you may want to load the locally compiled version of some GStreamer
24 plugin (e.g. Farstream) instead of the system installed one. To do so, just
25 set the GST_PLUGIN_PATH environment variable to tell GStreamer where your
26 plugins are located and the GST_PLUGIN_LOADING_WHITELIST to avoid conflicts
27 with system installed plugins. It's also a good idea to use GST_REGISTRY to
28 avoid clobbering your default GStreamer registry. For example you can
29 export these before launching the empathy processes as shown above:
30 export GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-plugins-good:libnice:farstream:gst-plugins-bad:gst-plugins-ugly:gst-ffmpeg
31 export GST_PLUGIN_PATH=/path/to/your/custom/lib/gstreamer-0.10
32 export GST_REGISTRY=/tmp/gstreamer.registry
34 See http://live.gnome.org/Empathy/ about coding style conventions.
35 See also http://live.gnome.org/Empathy/Git to read about our git workflow.