tree 30aa3b2a0564edccbab467e114791c93aae03a2c
parent be9a86f459f8e785bac42abcea5d13bd4ded251e
author David Benjamin <davidben@google.com> 1613685806 -0500
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1613751894 +0000

Future-proof vs_toolchain.py for VS2019.

In trying to figure out an ARM64 builder issue, I tried VS2019. That
didn't fix the ARM64 issue, but it did reveal that I ported over some of
the logic from Chromium wrong. For "new-style" paths, the toolchain
directory should be toolchain_data['path'], not the parent directory of
win_sdk.

(The latest VS2019 package in Chromium puts win_sdk a few directories
down from the toolchain root.)

This CL should be a no-op for now because all our current toolchains use
Chromium's "old-style" win_sdk-relative paths.

Change-Id: I8ad7784abb479d1ede3995a44433e57448e8debf
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45744
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>