Update Windows build instruction for 14393 SDK

Update Windows build instruction for 14393 SDK

The Windows build instructions mention that the 14393 SDK is needed but
now that 15063 has shipped the SDK is harder to find, leading some
developers to do problematic hacks. This adds a link to the archival
installer.

R=scottmg@chromium.org

Review-Url: https://codereview.chromium.org/2846643002
Cr-Commit-Position: refs/heads/master@{#467512}
Committed: https://chromium.googlesource.com/chromium/src/+/80610570ec4327389940e2ce084df9899692f42d

[brucedawson, 2017-04-26 22:28:45]

The CQ bit was checked by brucedawson@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-26 22:29:43]

Dry run: CQ is trying da patch.

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

[brucedawson, 2017-04-26 22:30:41]

Clarify the build instructions by saying where to get the 14393 SDK.

Some day Microsoft will ship a version of 15063 that can compile #include
<Bits.h> and then we won't need this anymore. They're working on it.

[commit-bot: I haz the power, 2017-04-26 22:43:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-26 22:43:51]

Dry run: This issue passed the CQ dry run.

[scottmg, 2017-04-26 23:06:30]

lgtm

https://codereview.chromium.org/2846643002/diff/1/docs/windows_build_instruct...
File docs/windows_build_instructions.md (right):

https://codereview.chromium.org/2846643002/diff/1/docs/windows_build_instruct...
docs/windows_build_instructions.md:39: found in the [Windows SDK
archive](https://developer.microsoft.com/en-us/windows/downloads/sdk-archive).
Maybe say 15063 is broken? Up to you.

[brucedawson, 2017-04-26 23:23:56]

https://codereview.chromium.org/2846643002/diff/1/docs/windows_build_instruct...
File docs/windows_build_instructions.md (right):

https://codereview.chromium.org/2846643002/diff/1/docs/windows_build_instruct...
docs/windows_build_instructions.md:39: found in the [Windows SDK
archive](https://developer.microsoft.com/en-us/windows/downloads/sdk-archive).
On 2017/04/26 23:06:30, scottmg wrote:
> Maybe say 15063 is broken? Up to you.

Done.

[brucedawson, 2017-04-26 23:23:59]

The CQ bit was checked by brucedawson@chromium.org

[brucedawson, 2017-04-26 23:23:59]

The patchset sent to the CQ was uploaded after l-g-t-m from scottmg@chromium.org
Link to the patchset: https://codereview.chromium.org/2846643002/#ps20001
(title: "Mentioned that 15063 is broken")

[commit-bot: I haz the power, 2017-04-26 23:25:24]

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, 2017-04-26 23:39:42]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1493249039499450,
"parent_rev": "c70faa8793b5c31d801f4c8e85f022bf904dc3e1", "commit_rev":
"80610570ec4327389940e2ce084df9899692f42d"}

[commit-bot: I haz the power, 2017-04-26 23:39:54]

Description was changed from

==========
Update Windows build instruction for 14393 SDK

The Windows build instructions mention that the 14393 SDK is needed but
now that 15063 has shipped the SDK is harder to find, leading some
developers to do problematic hacks. This adds a link to the archival
installer.

R=scottmg@chromium.org
==========

to

==========
Update Windows build instruction for 14393 SDK

The Windows build instructions mention that the 14393 SDK is needed but
now that 15063 has shipped the SDK is harder to find, leading some
developers to do problematic hacks. This adds a link to the archival
installer.

R=scottmg@chromium.org

Review-Url: https://codereview.chromium.org/2846643002
Cr-Commit-Position: refs/heads/master@{#467512}
Committed:
https://chromium.googlesource.com/chromium/src/+/80610570ec4327389940e2ce084d...
==========

[commit-bot: I haz the power, 2017-04-26 23:39:55]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/80610570ec4327389940e2ce084d...