Use gyp names in MIDL build rules rather than VS macros

build/common.gypi

 # Copyright (c) 2012 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.
 
 # IMPORTANT:
 # Please don't directly include this file if you are building via gyp_chromium,
 # since gyp_chromium is automatically forcing its inclusion.
 {
   # Variables expected to be overriden on the GYP command line (-D) or by
   # ~/.gyp/include.gypi.
@@ skipping 2815 matching lines @@
             # SubSystem values:
             #   0 == not set
             #   1 == /SUBSYSTEM:CONSOLE
             #   2 == /SUBSYSTEM:WINDOWS
             # Most of the executables we'll ever create are tests
             # and utilities with console output.
             'SubSystem': '1',
           },
           'VCMIDLTool': {
             'GenerateStublessProxies': 'true',
-            'TypeLibraryName': '$(InputName).tlb',
-            'OutputDirectory': '$(IntDir)',
-            'HeaderFileName': '$(InputName).h',
-            'DLLDataFileName': 'dlldata.c',
-            'InterfaceIdentifierFileName': '$(InputName)_i.c',
-            'ProxyFileName': '$(InputName)_p.c',
+            'TypeLibraryName': '<(RULE_INPUT_NAME).tlb',
+            'OutputDirectory': '<(INTERMEDIATE_DIR)',
+            'HeaderFileName': '<(RULE_INPUT_NAME).h',
+            'DLLDataFileName': '<(RULE_INPUT_NAME).dlldata.c',

[Mark Mentovai, 2012/03/30 12:54:27]

This is not equivalent to what you’re replacing. Is this an intentional change?

+            'InterfaceIdentifierFileName': '<(RULE_INPUT_NAME)_i.c',
+            'ProxyFileName': '<(RULE_INPUT_NAME)_p.c',
           },
           'VCResourceCompilerTool': {
             'Culture' : '1033',
             'AdditionalIncludeDirectories': [
               '<(DEPTH)',
               '<(SHARED_INTERMEDIATE_DIR)',
             ],
           },
         },
       },
@@ skipping 96 matching lines @@
     # settings in target dicts.  SYMROOT is a special case, because many other
     # Xcode variables depend on it, including variables such as
     # PROJECT_DERIVED_FILE_DIR.  When a source group corresponding to something
     # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
     # files to appear (when present) in the UI as actual files and not red
     # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
     # and therefore SYMROOT, needs to be set at the project level.
     'SYMROOT': '<(DEPTH)/xcodebuild',
   },
 }