Script to inline shader into C header file

remoting/client/opengl/BUILD.gn

Index: remoting/client/opengl/BUILD.gn
diff --git a/remoting/client/opengl/BUILD.gn b/remoting/client/opengl/BUILD.gn
new file mode 100644
index 0000000000000000000000000000000000000000..2231b5ea223de22279ba3ad220cf8e732919a227
--- /dev/null
+++ b/remoting/client/opengl/BUILD.gn
@@ -0,0 +1,18 @@
+shaders = [
+  "tex_coord_to_view.vert",
+  "draw_tex.frag",
+]
+
+action("inline_shaders") {
+  script = "../../tools/build/remoting_c_text_inliner.py"

[Jamie, 2016/06/04 00:24:37]

I think the script name would be better as something like shader_to_header.py.
It doesn't need to begin with remoting_ because it's implicit from its location
in the source, but it should say something about what the input is.

[Yuwei, 2016/06/04 01:31:42]

Done.

+  out_path = "${root_gen_dir}/remoting/client/opengl/shaders.h"
+  inputs = shaders
+  include_guard = "REMOTING_CLIENT_OPENGL_SHADERS_H_"

[Jamie, 2016/06/04 00:24:37]

Using the same include guard for every invocation of this rule means it can
effectively only be used once. I think it would be better to autogenerate it
(randomly) in the script itself.

[Yuwei, 2016/06/04 00:37:07]

Hmm... But I think this action should only be called once and there will only be
one header file for the shaders?

I agree that a randomly generated guard may be better...

[Yuwei, 2016/06/04 01:31:42]

Done.

+  outputs = [
+    out_path,
+  ]
+  args = [
+           include_guard,
+           rebase_path(out_path),
+         ] + rebase_path(shaders)
+}