In build/gyp_chromium, if CHROMIUM_GYP_SYNTAX_CHECK is set to 1, run gyp with --check.

In build/gyp_chromium, if CHROMIUM_GYP_SYNTAX_CHECK is set to 1, run gyp with --check.

This is to eventually run gyp with syntax checking enabled on the buildbots.
Enabling that will come in a later CL after all gyp errors are fixed.

BUG=none
TEST=none

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

[Mark Mentovai, 2010-03-26 17:53:45]

LGTM

http://codereview.chromium.org/1435001/diff/1/2
File build/gyp_chromium (right):

http://codereview.chromium.org/1435001/diff/1/2#newcode88
build/gyp_chromium:88: if syntax_check and int(syntax_check):
bool() is marginally closer to what you mean than int() and the effect is the
same.

[Robert Sesek, 2010-03-26 17:57:35]

http://codereview.chromium.org/1435001/diff/1/2
File build/gyp_chromium (right):

http://codereview.chromium.org/1435001/diff/1/2#newcode88
build/gyp_chromium:88: if syntax_check and int(syntax_check):
On 2010/03/26 17:53:45, Mark Mentovai wrote:
> bool() is marginally closer to what you mean than int() and the effect is the
> same.

That's what I thought, too. But |bool("0") == True| as does bool("1"). |bool(0)
== False|, though.

[Mark Mentovai, 2010-03-26 17:58:13]

Hmm, guess so.  LGTM, then.