Refactor the glib message-pump, and use it as the base for a gtk message pump and an X message pump.

media/media.gyp

Index: media/media.gyp
diff --git a/media/media.gyp b/media/media.gyp
index 87f9077163762c38d0509df2ee2f7ff8af3985ec..3a7aa720313d6b2bdedce234cb98042a13bfe3f9 100644
--- a/media/media.gyp
+++ b/media/media.gyp
@@ -678,6 +678,13 @@
             '../third_party/ffmpeg/ffmpeg.gyp:ffmpeg',
             '../third_party/openmax/openmax.gyp:il',
           ],
+          'conditions': [
+            ['touchui == 1', {
+              'dependencies': [
+                '../build/linux/system.gyp:gtk',

[Ami GONE FROM CHROMIUM, 2011/06/24 15:55:02]

This looks strange to me, since none of the sources listed below for this target
actually explicitly use GTK/GLIB (or MessagePump, for that matter).
From a short glance through the trybots I'm guessing you made this change to
address:
http://build.chromium.org/p/tryserver.chromium/builders/linux_touch/builds/18...
wouldn't a more principled fix be to have this stanza in base/base.gypi:base,
where message_pump_glib_x.cc and friends are pulled into the build in the first
place?

(i.e. doing it the way you propose requires adding this stanza to every binary
that depends on base, no?  I'm not seeing what's special about omx_test that it
should be different in this regard)

[sadrul, 2011/06/24 17:14:01]

omx_test.cc uses the message_loop. Would it be a good idea to have this always
depend on 'base' instead? I have added this, and this also fixes the problem.
I agree. This would definitely be the better way of doing things. (I honestly
didn't look into it too much since I noticed that omx_unittests does pull in
system.gyp:gtk explicitly, and this change will be removed anyway once we have
NativeWidgetX (soonish, http://codereview.chromium.org/7236030/))

+              ],
+            }],
+          ],
           'sources': [
             'tools/omx_test/color_space_util.cc',
             'tools/omx_test/color_space_util.h',