Fix installer_util_strings project with incredibuild....

Fix installer_util_strings project with incredibuild.

It was failing to generate $(OutDir)\obj\global_intermediate\installer_util_strings\installer_util_strings.*

TEST=none
BUG=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=25694

[M-A Ruel, 2009-09-08 20:34:59]

Tested on Google Chrome XP slave which was exhibiting the issue.

[M-A Ruel, 2009-09-08 20:52:22]

Added back direct_dependent_settings that I had stripped off by inadvertance.

[Nicolas Sylvain, 2009-09-08 20:54:29]

can you describe the patch is words please. That might make the change move
obvious.

[M-A Ruel, 2009-09-08 20:59:56]

In installer_util_strings, I changed from 'actions' to 'rules' so it is
generated as a VS-friendly format for dependency checking. Since it's not an
'action' anymore, I listed the .grd as a source file. I had to hardcode the
'inputs' since I couldn't figure how to make it a variable.

Removed the 'set PYTHONPATH.., '&&', '..../python.exe', ... which wasn't working
at all anyway. I pushed the PYTHONPATH fixup directly into create_string_rc.py,
I don't think this is a big deal.

create_string_rc.bat is not used so I removed it.

[bradn, 2009-09-08 21:14:37]

LGTM

This is great  (particularly that it works on the builder!!!) So are you saying
that incredibuild does not correctly handle the case where custom build steps
have outputs used by another module which is marked as dependent, but does
handle Custom build rule outputs? I know that in the past nsylvain and I had
perturbed this around until it started working, but understanding the cause
would be much better. 

Had you been seeing this fail with IB the way it currently was? What prompted
this? I've been blocked on bumping the gyp version because  it with gyp version
638 it will consistently fail on installer util strings. Ideally we'd try that
change on top of this (it changes some quoting, which was enough to make it
angry).

If there is a general issue like this with Custom Build Steps + IB, we need to
change the generator not to use them. It would seem this would have the
potential to affect all sorts of things.

http://codereview.chromium.org/196046/diff/2001/3001
File chrome/installer/installer.gyp (right):

http://codereview.chromium.org/196046/diff/2001/3001#newcode180
Line 180: 'type': 'dummy_executable',
Can this turn into 'none' after this change?

http://codereview.chromium.org/196046/diff/2001/3001#newcode192
Line 192: 'action': ['../../third_party/python_24/python.exe',
without msvs_cygwin_shell:0, you should be able to make this just 'python'