Don't confuse VS 2013 with VS 2017
Building with VS 2017 using a packaged toolchain is not yet supported but if you try to do it you get a surprising result - the VS 2013 toolchain gets downloaded. This adds a 2013 check to avoid this, and also simplifies/corrects an existing 2017 check and comment. This lets us fail-fast if a user tries the VS 2017 depot-tools combination before it is supported. BUG=683729 Review-Url: https://codereview.chromium.org/2741783006 Cr-Commit-Position: refs/heads/master@{#456226}
Showing
Please register or sign in to comment