Only build win static_initializers tool on Pro where DIA is available

Only build win static_initializers tool on Pro where DIA is available

Otherwise, 'all' fails when using Express toolchain.

R=grt@chromium.org
BUG=https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/j5xzCWuwam4

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

[grt (UTC plus 2), 2014-04-16 15:06:42]

lgtm if the answer to my question below is "no".

https://codereview.chromium.org/239603002/diff/1/tools/win/static_initializer...
File tools/win/static_initializers/static_initializers.gyp (right):

https://codereview.chromium.org/239603002/diff/1/tools/win/static_initializer...
tools/win/static_initializers/static_initializers.gyp:10:
['MSVS_VERSION=="2013"', {
can this me made to not break when 2014 comes around by either re-using the
variable msvs_express defined in common.gypi, or slicing off the last character
from MSVS_VERSION and comparing it with "e"?

[scottmg, 2014-04-16 17:09:03]

https://codereview.chromium.org/239603002/diff/1/tools/win/static_initializer...
File tools/win/static_initializers/static_initializers.gyp (right):

https://codereview.chromium.org/239603002/diff/1/tools/win/static_initializer...
tools/win/static_initializers/static_initializers.gyp:10:
['MSVS_VERSION=="2013"', {
On 2014/04/16 15:06:43, grt wrote:
> can this me made to not break when 2014 comes around by either re-using the
> variable msvs_express defined in common.gypi, or slicing off the last
character
> from MSVS_VERSION and comparing it with "e"?

Thanks! Switched to msvs_express.

[scottmg, 2014-04-16 17:09:14]

The CQ bit was checked by scottmg@chromium.org

[commit-bot: I haz the power, 2014-04-16 17:10:52]

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

[commit-bot: I haz the power, 2014-04-16 21:15:58]

Change committed as 264305