remoting: fix out-of-tree build

remoting/host/BUILD.gn

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 import("//build/config/features.gni")
 import("//build/config/ui.gni")
 import("//build/config/win/manifest.gni")
 import("//build/util/version.gni")
 import("//remoting/remoting_enable.gni")
 import("//remoting/remoting_locales.gni")
@@ skipping 716 matching lines @@
     action_foreach("remoting_native_messaging_manifests") {
       if (is_mac) {
         assert(false, "not implemented on mac yet")
       } else {
         me2me_host_path =
             "/opt/google/chrome-remote-desktop/native-messaging-host"
         it2me_host_path =
             "/opt/google/chrome-remote-desktop/remote-assistance-host"
       }
 
-      script = "../tools/build/remoting_localize.py"
+      script = rebase_path("//remoting/tools/build/remoting_localize.py")

[brettw, 2016/05/04 16:41:39]

I don't understand this change. "script" is a built-in variable that GN
interprets to be relative to the current directory. Why does making this be
system-absolute fix anything?

[Paweł Hajdan Jr., 2016/05/05 13:22:55]

It wasn't needed. Removed these changes. I didn't realize the relative path is
preferred in this case.

 
       sources = [
         "it2me/com.google.chrome.remote_assistance.json.jinja2",
         "setup/com.google.chrome.remote_desktop.json.jinja2",
       ]
 
       inputs = [
         branding_path,
       ]
 
@@ skipping 396 matching lines @@
           "--target_arch",
           "$target_cpu",
           rebase_path("$root_out_dir/remoting-me2me-host-$current_os.zip",
                       root_build_dir),
           rebase_path(outputs[0], root_build_dir),
         ]
       }
     }
   }
 }