When the Creators Update SDK (10.0.15063.0) came out it was buggy so we locked Chrome builds to to the Anniversary Edition SDK (10.0.14393.0).
However this means that if developers only install the latest SDK they cannot build Chrome. This is particularly frustrating for developers who want to build Chrome with VS 2017, which now ships with 10.0.15063.0.
Since the 10.0.15063.468 SDK fixes the bugs this change removes the SDK limitation. Builds with the local toolchain will now use the latest SDK version installed. 10.0.14393.0 is the minimum.
Build machine builds are unaffected as they don't use an installed toolchain.
If you hit a build error with bits10_1.h not being found then install the latest Windows 10 SDK. If you do a clang build and hit a build error with undeclared identifier 'DefaultDelegateCheckMode then install the latest Windows 10 SDK.
The 10.0.15063.0 SDK will probably be required at some point.
I tested this on a machine that has VS 2017 with 15063 installed but no 14393 SDK. Without the patch there were cryptic failures because mc.exe and windows.h could not be found at build time. With the patch the build worked.
Change-Id: Ie74dac40b5b26e19153f173cc2b54e926ee1c917 Reviewed-on: https://chromium-review.googlesource.com/565421
48bee70 Allow building with the Creators Update SDK
build/toolchain/win/setup_toolchain.py | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)