05a5beb35c
- Pull in a trimmed down version of vs_toolchain.py from Chromium. - Drop in toolchain_vs2013.hash from Chromium to use Chromium's current toolchain. - Add a very hacky vs_env.py to pull in Visual Studio. This is loosely based off a handful of lines of Chromium's tools/clang/scripts/update.py. This (and vs_toolchain.py) depends on gyp which is now pulled in via DEPS. BUG=430237 Change-Id: Ic29cbb15e19a99616cfe778d0778b9a71c45338a Reviewed-on: https://boringssl-review.googlesource.com/3900 Reviewed-by: Adam Langley <agl@google.com> |
||
---|---|---|
.. | ||
go | ||
cmake-linux64.tar.gz.sha1 | ||
cmake-mac.tar.gz.sha1 | ||
cmake-win32.zip.sha1 | ||
DEPS | ||
extract.py | ||
perl-win32.zip.sha1 | ||
README | ||
toolchain_vs2013.hash | ||
vs_env.py | ||
vs_toolchain.py | ||
yasm-win32.exe.sha1 |
This directory contains tools for setting up a hermetic toolchain on the continuous integration bots. It is in the repository for convenience and can be ignored in development.