Copy Linux me2me script to output dir for GN builds

remoting/host/BUILD.gn

Index: remoting/host/BUILD.gn
diff --git a/remoting/host/BUILD.gn b/remoting/host/BUILD.gn
index 29c7e33fbcf409e758829db12f4be9e763265ec6..9a42df23d9747401caa748cc75a4ec1acd7ad3f4 100644
--- a/remoting/host/BUILD.gn
+++ b/remoting/host/BUILD.gn
@@ -843,6 +843,21 @@ if (is_mac) {  # TODO(GYP) Mac build of remoting host.
           ":remoting_me2me_host_static",
           "//build/config/sanitizers:deps",
         ]
+
+        if (is_linux) {
+          deps += [ ":remoting_me2me_host_runner" ]
+        }
+      }
+
+      if (is_linux) {
+        copy("remoting_me2me_host_runner") {
+          sources = [
+            "linux/linux_me2me_host.py",
+          ]
+          outputs = [
+            "$root_build_dir/run_me2me_host",

[Sergey Ulanov, 2016/04/14 23:49:06]

It's confusing to use 3 different name for the same script depending on where
it's placed.

Also for people who don't work on remoting it will be confusing to see this file
in the shared output directory, as they have not idea what is "me2me_host". We
should either put our stuff under out/<..>/remoting or have remoting_ prefix for
all files. In this case I think we want to put it under a separate directory (as
we don't to rename the file). But then the host binary has to be moved as well.
How about we just use the same name that we use in
/opt/google/chrome-remote-desktop/, i.e.:

out/<..>/remoting/chrome-remote-desktop (the python script)
out/<..>/remoting/chrome-remote-desktop-host (the host binary)

That way we won't need anything special in the python script to handle the dev
mode. WDYT?

+          ]
+        }
       }
 
       executable("native_messaging_host") {