Use gyp names in MIDL build rules rather than VS macros

Use gyp names in MIDL build rules rather than VS macros.

In support of ninja/windows. DLLDataFileName changed to be uniquized too because in a target that has multiple idl files, they would all output to the same dlldata.c (which ninja quite reasonably doesn't like).

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=129968

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

LGTM if intentional.

https://chromiumcodereview.appspot.com/9460048/diff/3001/build/common.gypi
File build/common.gypi (right):

https://chromiumcodereview.appspot.com/9460048/diff/3001/build/common.gypi#ne...
build/common.gypi:2839: 'DLLDataFileName': '<(RULE_INPUT_NAME).dlldata.c',
This is not equivalent to what you’re replacing. Is this an intentional change?

[scottmg, 2012-03-30 19:01:12]

On 2012/03/30 12:54:27, Mark Mentovai wrote:
> LGTM if intentional.
> 

Thanks. Yes, intentional. Noted in description.

[commit-bot: I haz the power, 2012-03-30 19:19:24]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/scottmg@chromium.org/9460048/3001

[commit-bot: I haz the power, 2012-03-30 22:10:34]

Try job failure for 9460048-3001 (retry) on win_rel for steps "ui_tests,
browser_tests".
It's a second try, previously, steps "ui_tests, browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...