GN files for running Closure Compiler

third_party/jstemplate/BUILD.gn

Index: third_party/jstemplate/BUILD.gn
diff --git a/third_party/jstemplate/BUILD.gn b/third_party/jstemplate/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..9a35cc419c515ca9257128c3fe3f23557fd18f81
--- /dev/null
+++ b/third_party/jstemplate/BUILD.gn
@@ -0,0 +1,22 @@
+# Copyright 2016 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("//third_party/closure_compiler/compile_js2.gni")
+
+compile_js("compile_util") {

[Dan Beam, 2016/09/06 16:46:46]

why are we prefixing with compile_ everywhere?  what's the value?  this is
mainly typechecking right now, and this differs from the old system (as it adds
a lot of fluff to every target name).

this already reads as "compile JS <name>".  with the "compile_" prefix it reads
as "compile JS compile <name>", i.e. "compile the compiled thing" (IMO)

[aberent, 2016/09/06 17:30:22]

The issue is that one can't have multiple BUILD.gn files in a single directory,
so target names have to be unique within a directory. If, as is the case with
braille_ime, the folder already has (or could in future contain) targets that
are part of the main build we want to be sure that our target names wont
conflict with them. It seemed to me that using just the file name root as the
target name (as we do in GYP) was quite likely to conflict, so I invented the
convention of adding compile_ to the front of these target names.

+  source_files = [ "util.js" ]
+}
+
+compile_js("compile_jsevalcontext") {
+  source_files = [ "jsevalcontext.js" ]
+  deps = [
+    ":compile_util",
+  ]
+}
+
+compile_js("compile_jstemplate") {
+  source_files = [ "jstemplate.js" ]
+  deps = [
+    ":compile_jsevalcontext",
+  ]
+}