Better code to determine the framework and helper app paths

chrome/chrome.gyp

Index: chrome/chrome.gyp
===================================================================
--- chrome/chrome.gyp	(revision 28999)
+++ chrome/chrome.gyp	(working copy)
@@ -469,6 +469,28 @@
         'common/pref_names.cc',
         'common/pref_names.h',
       ],
+      'actions': [
+        {
+          'action_name': 'Make chrome_version.cc',
+          'variables': {
+            'make_version_cc_path': 'tools/build/make_version_cc.py',
+          },
+          'inputs': [
+            '<(make_version_cc_path)',
+            'VERSION',
+          ],
+          'outputs': [
+            '<(INTERMEDIATE_DIR)/chrome_version.cc',
+          ],
+          'action': [
+            'python',
+            '<(make_version_cc_path)',
+            '<@(_outputs)',
+            '<(version_full)',
+          ],
+          'process_outputs_as_sources': 1,
+        },

[TVL, 2009/10/14 21:09:15]

see base.gyp:linux_versioninfo, yes, it reached up into the chrome directory.  
I know i've seen complaints on that building too often in the past, so this
seems like something related that we should be careful about.

[Mark Mentovai, 2009/10/14 21:26:46]

TVL wrote:
I think that the main problem with linux_versioninfo is that it embeds the SVN
revision.  That can change a lot more frequently than VERSION.

+      ],
     },
     {
       'target_name': 'common',