Add an option to build with the 10.0.14393 SDK

Add an option to build with the 10.0.14393 SDK

At some point we may need to build with the 10.0.14393 (Windows 10
Anniversary Edition) SDK. It's all packaged up and ready to go, and
this is as good a way as any to record what the hash is for when we
need it.

Any Google employee developing Chrome on Windows can test this out by
setting DEPOT_TOOLS_WIN_SDK_PRERELEASE=1 and running gclient
runhooks.

BUG=440500
Committed: https://crrev.com/5456b380fd8b29d954ad293c19d13b18b975f166
Cr-Commit-Position: refs/heads/master@{#431387}

[brucedawson, 2016-11-10 01:19:11]

brucedawson@chromium.org changed reviewers:
+ scottmg@chromium.org

[brucedawson, 2016-11-10 01:19:11]

Might as well make this available for testing purposes? That way we'll be more
clearly ready if/when we need to switch to the 10.0.14393 SDK.

I think it builds cleanly with the environment variable set, but if it doesn't
we should still land this.

[scottmg, 2016-11-10 01:30:01]

lgtm

https://codereview.chromium.org/2492573002/diff/1/build/vs_toolchain.py
File build/vs_toolchain.py (right):

https://codereview.chromium.org/2492573002/diff/1/build/vs_toolchain.py#newco...
build/vs_toolchain.py:314: else:
Maybe delete the 2013 hash while you're at it.

[brucedawson, 2016-11-10 21:51:56]

> Maybe delete the 2013 hash while you're at it.

I'm inclined to leave it because it serves as a bread-crumb reminder of where to
insert changes when we want to support 2017. And also because removing it from
there would suggest we should delete it from many other places in this file and
others, and I'm not enthused about that except for things that we will never
need to bring back.

[brucedawson, 2016-11-10 21:52:21]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2016-11-10 21:53:00]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-10 22:57:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-10 23:10:34]

Description was changed from

==========
Add an option to build with the 10.0.14393 SDK

At some point we may need to build with the 10.0.14393 (Windows 10
Anniversary Edition) SDK. It's all packaged up and ready to go, and
this is as good a way as any to record what the hash is for when we
need it.

Any Google employee developing Chrome on Windows can test this out by
setting DEPOT_TOOLS_WIN_SDK_PRERELEASE=1 and running gclient
runhooks.

BUG=440500
==========

to

==========
Add an option to build with the 10.0.14393 SDK

At some point we may need to build with the 10.0.14393 (Windows 10
Anniversary Edition) SDK. It's all packaged up and ready to go, and
this is as good a way as any to record what the hash is for when we
need it.

Any Google employee developing Chrome on Windows can test this out by
setting DEPOT_TOOLS_WIN_SDK_PRERELEASE=1 and running gclient
runhooks.

BUG=440500

Committed: https://crrev.com/5456b380fd8b29d954ad293c19d13b18b975f166
Cr-Commit-Position: refs/heads/master@{#431387}
==========

[commit-bot: I haz the power, 2016-11-10 23:10:35]

Patchset 1 (id:??) landed as
https://crrev.com/5456b380fd8b29d954ad293c19d13b18b975f166
Cr-Commit-Position: refs/heads/master@{#431387}