Generate version resources for Chrome Frame using the same machinery as Chrome itself.

chrome/version.gypi

Index: chrome/version.gypi
diff --git a/chrome/version.gypi b/chrome/version.gypi
index 7b1338517c8314ebe7f1484805e9c3f05d0aed37..f1af6fdc9bdceb2ea1dbb707890de79280c3d842 100644
--- a/chrome/version.gypi
+++ b/chrome/version.gypi
@@ -5,7 +5,7 @@
 {
   'variables': {
     'variables': {
-      'version_py_path': 'tools/build/version.py',
+      'version_py_path': '<(DEPTH)/chrome/tools/build/version.py',

[robertshield, 2012/10/15 13:58:14]

I had heard that we weren't supposed to use DEPTH anymore. Is it necessary here?

[grt (UTC plus 2), 2012/10/15 14:43:24]

This .gypi file is now being included by .gyp files in different directories.  I
think DEPTH is needed to handle this.  DEPTH occurs many times in
build/common.gypi for the same reason, I believe.  Indeed, I just discovered
this from a thread on chromium-dev:

"When it does appear, it's within a GYPI file. This is intentional, due to how
pathname relativization/canonicalization happens with GYP includes - paths are
made relative to the including GYP, rather than to the (current) GYPI file,
therefore it's necessary to specify <(DEPTH) to ensure that, regardless of where
the including GYP file lives, the paths referenced are correct.

Even within GYPI, this is not a frequent thing - it's only for "utility GYPI"
files such as protoc or the Chrome for Android java helpers."

This is such a utility GYPI file that's intended to be included by GYP files
outside of this project.

       'version_path': 'VERSION',
     },
     'version_py_path': '<(version_py_path)',