eaf0a17db8
This is to transition BoringSSL's Windows build from Yasm to NASM. This change itself is a no-op for now, but a later change to the BoringSSL recipes will add a pair of standalone builders here. Then I'll get the change I have lying around for Chromium moving. Bug: chromium:766721 Change-Id: I4dca1c299f93bc5c01695983fe0478490c472deb Reviewed-on: https://boringssl-review.googlesource.com/29324 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
---|---|---|
.. | ||
go | ||
cmake-linux64.tar.gz.sha1 | ||
cmake-mac.tar.gz.sha1 | ||
cmake-win32.zip.sha1 | ||
DEPS | ||
extract.py | ||
nasm-win32.exe.sha1 | ||
perl-win32.zip.sha1 | ||
README | ||
sde-linux64.tar.bz2.sha1 | ||
update_clang.py | ||
UPDATING | ||
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.