From 212bafd6109eb01654065527a8dd55206ecaf535 Mon Sep 17 00:00:00 2001
From: Lennart Poettering <lennart@poettering.net>
Date: Mon, 23 Mar 2009 21:37:17 +0100
Subject: Detect forks

Some really stupid applications (Hey, vim, that means you!)
love to fork after initializing gtk/libcanberra. This is really
bad style. We however have to deal with this cleanly, so we try
to detect the forks making sure all our calls fail cleanly
after the fork.
---
 src/Makefile.am | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'src/Makefile.am')

diff --git a/src/Makefile.am b/src/Makefile.am
index 1fb5168..e40ec1f 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -52,7 +52,8 @@ libcanberra_la_SOURCES = \
 	sound-theme-spec.c sound-theme-spec.h \
 	llist.h \
 	macro.h macro.c \
-	malloc.c malloc.h
+	malloc.c malloc.h \
+	fork-detect.c fork-detect.h
 libcanberra_la_CFLAGS = \
 	$(AM_CFLAGS) \
 	$(VORBIS_CFLAGS)
-- 
cgit