Fix gyp failure on linux when use_ozone=1 is set

build/gn_migration.gypi

Index: build/gn_migration.gypi
diff --git a/build/gn_migration.gypi b/build/gn_migration.gypi
index f9a4db868a12ac3255d21af2698352e868c73bba..1d14cd8eb503948db95a32b434b11c643821baa0 100644
--- a/build/gn_migration.gypi
+++ b/build/gn_migration.gypi
@@ -240,7 +240,7 @@
             '../remoting/remoting_all.gyp:remoting_all',
           ],
         }],
-        ['remoting==1 and chromeos==0', {
+        ['remoting==1 and chromeos==0 and use_x11==1', {

[Dirk Pranke, 2015/05/18 20:44:16]

This seems to be the right change to at least match what we do in
remoting/remoting_enable.gypi, but this doesn't actually solve the bug (which is
a gyp bug), right?

[babu, 2015/05/19 11:10:53]

Thanks for reviewing, Dirk!

This fixes the build error for me. My understanding is that the
gn_migration.gypi is adding remoting_me2me_* targets, but those targets are not
enabled in remoting/remoting_host.gypi when use_x11=0 and that is causing build
failure in the Linux builds. I might be wrong here though.

This patch fixes the issue by not trying to include those targets in
gn_migration.gypi when use_x11=0.

[Dirk Pranke, 2015/05/19 19:54:47]

Oh, I'm sorry, I totally misread this and thought you were modifying a GN file
:(.

lgtm.

           'dependencies': [
             '../remoting/remoting.gyp:remoting_me2me_host',
             '../remoting/remoting.gyp:remoting_me2me_native_messaging_host',