Repackaged VS 2017 with updated SetEnv.cmd

Clang sanitizer tests don't build with MSVC2017 SDK due to a missing
environment variable. The packaging script has been updated to provide
that in the future but this is just a repackaging of the previous
package with a spot-fix, using a new --repackage option to
win_toolchain/package_from_installed.py.

To test this I did a "gclient runhooks" to pull down the new package
and then did a directory compare. This verified that the only file
that is changed is SetEnv.cmd and the only change there is to add:

set VCToolsInstallDir=%~dp0..\..\VC\Tools\MSVC\14.11.25503\

So, this should give identical results to the previous package except
in the case where VCToolsInstallDir is needed.

Bug: 772123
Change-Id: I70644d24e306825abbb4245802c7c3234c4b54dc
Reviewed-on: https://chromium-review.googlesource.com/713441
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#508151}

CrOS-Libchrome-Original-Commit: 5aed7b7bbfb9311aa80b293c8d9e21f099fff776
1 file changed
tree: 3b3fa0f2faadd55cb6dc165d569685bb1e0f0d11
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/