kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
5ce12e6436
boringssl/util/bot/UPDATING

85 lines
3.7 KiB
Plaintext
Raw Normal View History

Update versions of tools in util/bot. Update the easy ones here. Also include instructions on how to do this. The .sha1 files will be updated separately with instructions. Change-Id: I2a3aba43b8ffbdf930b8a2602dc1460077f6d0e7 Reviewed-on: https://boringssl-review.googlesource.com/7412 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 22:46:47 +00:00
This directory consumes tools from other repositories for use on the
Update tools. Change-Id: Idb6818ad9b6af2b1cb604e71d936aaca7210aa57 Reviewed-on: https://boringssl-review.googlesource.com/30624 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2018-08-09 19:40:34 +01:00
bots. For a similarly-configured local checkout for testing, run:
mkdir boringssl-gclient
cd boringssl-gclient
gclient config --unmanaged --deps-file=util/bot/DEPS https://boringssl.googlesource.com/boringssl/
gclient sync
To update to newer revisions, follow these instructions:
Update versions of tools in util/bot. Update the easy ones here. Also include instructions on how to do this. The .sha1 files will be updated separately with instructions. Change-Id: I2a3aba43b8ffbdf930b8a2602dc1460077f6d0e7 Reviewed-on: https://boringssl-review.googlesource.com/7412 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 22:46:47 +00:00
Pull Chromium's android_tools as an android-only dependency. This will be used by the bots to get adb and the NDK. BUG=26 Change-Id: Iae07a380c49b4990f0aa7d73c4f0b399924b9784 Reviewed-on: https://boringssl-review.googlesource.com/7986 Reviewed-by: Adam Langley <agl@google.com>
2016-05-19 05:33:41 +01:00
DEPS: Set all revisions to those used in Chromium, found at
https://chromium.googlesource.com/chromium/src/+/master/DEPS (Search for the
corresponding repository name.)
Update versions of tools in util/bot. Update the easy ones here. Also include instructions on how to do this. The .sha1 files will be updated separately with instructions. Change-Id: I2a3aba43b8ffbdf930b8a2602dc1460077f6d0e7 Reviewed-on: https://boringssl-review.googlesource.com/7412 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 22:46:47 +00:00
go/bootstrap.py: Set TOOLSET_VERSION to the latest release of Go, found at
https://golang.org/dl/.
update_clang.py: Set CLANG_REVISION and CLANG_SUB_REVISION to the values used in
Chromium, found at
https://chromium.googlesource.com/chromium/src/+/master/tools/clang/scripts/update.py
Teach vs_toolchain.py to load both MSVC 2015 and 2017. The default is still 2015, but I'll use this to spin up some 2017 bots as well. Change-Id: Id189791c5c50ae5403f7d6db1cd486f8a3f43dfa Reviewed-on: https://boringssl-review.googlesource.com/21165 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-10-05 18:40:33 +01:00
vs_toolchain.py: Update _GetDesiredVsToolchainHashes from Chromium, found at
Update versions of tools in util/bot. Update the easy ones here. Also include instructions on how to do this. The .sha1 files will be updated separately with instructions. Change-Id: I2a3aba43b8ffbdf930b8a2602dc1460077f6d0e7 Reviewed-on: https://boringssl-review.googlesource.com/7412 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 22:46:47 +00:00
https://chromium.googlesource.com/chromium/src/+/master/build/vs_toolchain.py
Teach vs_toolchain.py to load both MSVC 2015 and 2017. The default is still 2015, but I'll use this to spin up some 2017 bots as well. Change-Id: Id189791c5c50ae5403f7d6db1cd486f8a3f43dfa Reviewed-on: https://boringssl-review.googlesource.com/21165 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-10-05 18:40:33 +01:00
This may require taking other updates to that file. (Don't remove MSVC
versions if BoringSSL still needs to support them.)
Update versions of tools in util/bot. Update the easy ones here. Also include instructions on how to do this. The .sha1 files will be updated separately with instructions. Change-Id: I2a3aba43b8ffbdf930b8a2602dc1460077f6d0e7 Reviewed-on: https://boringssl-review.googlesource.com/7412 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 22:46:47 +00:00
Update Windows tools for the bots. See 0d5e080ab948da74be68e5f9f6c002fedc99a3ec for the previous version. Include instructions on where to get the tools used. 807f96230c889b10f2957a47585426af4cdb116a8a77f1caecca83b7d7ab862b cmake-3.5.0-win32-x86.zip e6bb5c3e4d936bb1067560a58a21260693a0fbe34e55afb0111fe14f7eebc92c strawberry-perl-5.22.1.2-32bit-portable.zip Change-Id: I504cf779abce26087d09c0c974fb481886c9c459 Reviewed-on: https://boringssl-review.googlesource.com/7413 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:05:12 +00:00
The .sha1 files correspond to files downloaded from Google Cloud Storage. To
update, place the updated files in their intended location and run:
upload_to_google_storage.py -b chromium-tools FILE
Update cmake-linux64.tar.gz and cmake-mac.tar.gz. Built from: 92c83ad8a4fd6224cf6319a60b399854f55b38ebe9d297c942408b792b1a9efa cmake-3.5.0.tar.gz Update instructions in the UPDATING file. Change-Id: I49d3f5ef353347c446a04797719227e9793e3e0d Reviewed-on: https://boringssl-review.googlesource.com/7414 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:40:04 +00:00
cmake-linux64.tar.gz: Download the latest CMake source tarball, found at
https://cmake.org/download/. Build it with:
./bootstrap --prefix=$PWD/cmake-linux64 && make && make install
tar -czf cmake-linux64.tar.gz cmake-linux64/
Update CMake to 3.10.0 on the bots. The NDK toolchain file requires 3.6.0 or later. We were still using 3.5.0. Change-Id: I216d33bed4187c7e62a2672eb4f92ce815b60b1c Reviewed-on: https://boringssl-review.googlesource.com/24104 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-12-13 19:40:31 +00:00
The current revision was built against cmake-3.10.0.tar.gz.
Update other bot tools. Also document what versions of everything we're using as the .sha1 files don't say. Change-Id: I2d496c86761f6df6acd20e1af62094b7d89e5c1d Reviewed-on: https://boringssl-review.googlesource.com/17485 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2017-06-29 20:26:05 +01:00
Update cmake-linux64.tar.gz and cmake-mac.tar.gz. Built from: 92c83ad8a4fd6224cf6319a60b399854f55b38ebe9d297c942408b792b1a9efa cmake-3.5.0.tar.gz Update instructions in the UPDATING file. Change-Id: I49d3f5ef353347c446a04797719227e9793e3e0d Reviewed-on: https://boringssl-review.googlesource.com/7414 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:40:04 +00:00
cmake-mac.tar.gz: Follow the same instructions as above on a Mac, but replace
cmake-linux64 with cmake-mac.
Update CMake to 3.10.0 on the bots. The NDK toolchain file requires 3.6.0 or later. We were still using 3.5.0. Change-Id: I216d33bed4187c7e62a2672eb4f92ce815b60b1c Reviewed-on: https://boringssl-review.googlesource.com/24104 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-12-13 19:40:31 +00:00
The current revision was built against cmake-3.10.0.tar.gz.
Update other bot tools. Also document what versions of everything we're using as the .sha1 files don't say. Change-Id: I2d496c86761f6df6acd20e1af62094b7d89e5c1d Reviewed-on: https://boringssl-review.googlesource.com/17485 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2017-06-29 20:26:05 +01:00
Update Windows tools for the bots. See 0d5e080ab948da74be68e5f9f6c002fedc99a3ec for the previous version. Include instructions on where to get the tools used. 807f96230c889b10f2957a47585426af4cdb116a8a77f1caecca83b7d7ab862b cmake-3.5.0-win32-x86.zip e6bb5c3e4d936bb1067560a58a21260693a0fbe34e55afb0111fe14f7eebc92c strawberry-perl-5.22.1.2-32bit-portable.zip Change-Id: I504cf779abce26087d09c0c974fb481886c9c459 Reviewed-on: https://boringssl-review.googlesource.com/7413 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:05:12 +00:00
cmake-win32.zip: Update to the latest prebuilt release of CMake, found at
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
https://cmake.org/download/. Use the file labeled "Windows win64-x64
ZIP". The download will be named cmake-VERSION-win64-x64.zip.
Update Windows tools for the bots. See 0d5e080ab948da74be68e5f9f6c002fedc99a3ec for the previous version. Include instructions on where to get the tools used. 807f96230c889b10f2957a47585426af4cdb116a8a77f1caecca83b7d7ab862b cmake-3.5.0-win32-x86.zip e6bb5c3e4d936bb1067560a58a21260693a0fbe34e55afb0111fe14f7eebc92c strawberry-perl-5.22.1.2-32bit-portable.zip Change-Id: I504cf779abce26087d09c0c974fb481886c9c459 Reviewed-on: https://boringssl-review.googlesource.com/7413 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:05:12 +00:00
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
The current revision is cmake-3.11.4-win64-x64.zip
Update other bot tools. Also document what versions of everything we're using as the .sha1 files don't say. Change-Id: I2d496c86761f6df6acd20e1af62094b7d89e5c1d Reviewed-on: https://boringssl-review.googlesource.com/17485 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2017-06-29 20:26:05 +01:00
Add a copy of NASM to util/bot/ in BoringSSL. 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>
2018-06-22 22:36:15 +01:00
nasm-win32.exe: Update to the appropriate release of NASM, found at
https://www.nasm.us/. Use the same version as Chromium, found at
https://chromium.googlesource.com/chromium/src/+/master/third_party/nasm/README.chromium
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
Extract nasm.exe from the download named nasm-VERSION-win64.zip.
Add a copy of NASM to util/bot/ in BoringSSL. 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>
2018-06-22 22:36:15 +01:00
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
The current revision is nasm-2.13.03-win64.zip.
Add a copy of NASM to util/bot/ in BoringSSL. 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>
2018-06-22 22:36:15 +01:00
TODO(davidben): The Chromium link currently does not work. It will get
filled in in the future. See https://crbug.com/766721.
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
perl-win32.zip: Update to the latest 64-bit prebuilt "Portable" edition of
Update Windows tools for the bots. See 0d5e080ab948da74be68e5f9f6c002fedc99a3ec for the previous version. Include instructions on where to get the tools used. 807f96230c889b10f2957a47585426af4cdb116a8a77f1caecca83b7d7ab862b cmake-3.5.0-win32-x86.zip e6bb5c3e4d936bb1067560a58a21260693a0fbe34e55afb0111fe14f7eebc92c strawberry-perl-5.22.1.2-32bit-portable.zip Change-Id: I504cf779abce26087d09c0c974fb481886c9c459 Reviewed-on: https://boringssl-review.googlesource.com/7413 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:05:12 +00:00
Strawberry Perl, found at http://strawberryperl.com/releases.html. The
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
download will be named strawberry-perl-VERSION-64bit-portable.zip.
Update Windows tools for the bots. See 0d5e080ab948da74be68e5f9f6c002fedc99a3ec for the previous version. Include instructions on where to get the tools used. 807f96230c889b10f2957a47585426af4cdb116a8a77f1caecca83b7d7ab862b cmake-3.5.0-win32-x86.zip e6bb5c3e4d936bb1067560a58a21260693a0fbe34e55afb0111fe14f7eebc92c strawberry-perl-5.22.1.2-32bit-portable.zip Change-Id: I504cf779abce26087d09c0c974fb481886c9c459 Reviewed-on: https://boringssl-review.googlesource.com/7413 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:05:12 +00:00
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
The current revision is strawberry-perl-5.26.2.1-64bit-portable.zip.
Update other bot tools. Also document what versions of everything we're using as the .sha1 files don't say. Change-Id: I2d496c86761f6df6acd20e1af62094b7d89e5c1d Reviewed-on: https://boringssl-review.googlesource.com/17485 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2017-06-29 20:26:05 +01:00
Update Windows tools for the bots. See 0d5e080ab948da74be68e5f9f6c002fedc99a3ec for the previous version. Include instructions on where to get the tools used. 807f96230c889b10f2957a47585426af4cdb116a8a77f1caecca83b7d7ab862b cmake-3.5.0-win32-x86.zip e6bb5c3e4d936bb1067560a58a21260693a0fbe34e55afb0111fe14f7eebc92c strawberry-perl-5.22.1.2-32bit-portable.zip Change-Id: I504cf779abce26087d09c0c974fb481886c9c459 Reviewed-on: https://boringssl-review.googlesource.com/7413 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>
2016-03-09 23:05:12 +00:00
yasm-win32.exe: Update to the appropriate release of Yasm. Use the same version
as Chromium, found at
https://chromium.googlesource.com/chromium/src/+/master/third_party/yasm/README.chromium
Use the release at http://yasm.tortall.net/Download.html labeled
"Win32 .exe". The download will be named yasm-VERSION-win32.exe.
Update to the latest Intel SDE. efa4339adde7e627370ed7c46ed00fed5d23310007ef0334ae17510d00e22b8d sde-external-8.5.0-2017-06-08-lin.tar.bz2 Change-Id: I201ca78cbbb3c769ed45705f87b6013758b68349 Reviewed-on: https://boringssl-review.googlesource.com/17484 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com>
2017-06-29 20:10:59 +01:00
Update yasm to 1.3.0 on the bots. As of https://chromium-review.googlesource.com/#/c/608869/, Chromium is now using yasm 1.3.0, which means we can rely on it. This is upstream's yasm-1.3.0-win32.exe which has a SHA-512 hash of: 850b26be5bbbdaeaf45ac39dd27f69f1a85e600c35afbd16b9f621396b3c7a19863ea3ff316b025b578fce0a8280eef2203306a2b3e46ee1389abb65313fb720 (I'm using such a humungous hash because if one searches for it on Google, there is evidence that someone else in the world downloaded the same hash.) Change-Id: I4674080dd07d3e07f399a67e767a00fc67d4aa63 Reviewed-on: https://boringssl-review.googlesource.com/19104 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com>
2017-08-11 04:31:28 +01:00
The current revision is yasm-1.3.0-win32.exe.
Update other bot tools. Also document what versions of everything we're using as the .sha1 files don't say. Change-Id: I2d496c86761f6df6acd20e1af62094b7d89e5c1d Reviewed-on: https://boringssl-review.googlesource.com/17485 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2017-06-29 20:26:05 +01:00
Update SDE and add the Windows version. Windows is sufficiently different from Linux that running tests under SDE for Windows, particularly with the new ABI tests, is worthwhile. Change-Id: I32c4f6de06b2e732ebb2c1492eb1766cae73c0e0 Reviewed-on: https://boringssl-review.googlesource.com/c/34064 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com>
2019-01-03 20:42:36 +00:00
Finally, update sde-linux64.tar.bz2 and sde-win32.tar.bz2 by downloading the
latet release from Intel at
Update to the latest Intel SDE. efa4339adde7e627370ed7c46ed00fed5d23310007ef0334ae17510d00e22b8d sde-external-8.5.0-2017-06-08-lin.tar.bz2 Change-Id: I201ca78cbbb3c769ed45705f87b6013758b68349 Reviewed-on: https://boringssl-review.googlesource.com/17484 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com>
2017-06-29 20:10:59 +01:00
https://software.intel.com/en-us/articles/intel-software-development-emulator,
but upload it with the following command. (Note the bucket is different.)
Update SDE and add the Windows version. Windows is sufficiently different from Linux that running tests under SDE for Windows, particularly with the new ABI tests, is worthwhile. Change-Id: I32c4f6de06b2e732ebb2c1492eb1766cae73c0e0 Reviewed-on: https://boringssl-review.googlesource.com/c/34064 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com>
2019-01-03 20:42:36 +00:00
upload_to_google_storage.py -b chrome-boringssl-sde sde-linux64.tar.bz2 sde-win32.tar.bz2
Update other bot tools. Also document what versions of everything we're using as the .sha1 files don't say. Change-Id: I2d496c86761f6df6acd20e1af62094b7d89e5c1d Reviewed-on: https://boringssl-review.googlesource.com/17485 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
2017-06-29 20:26:05 +01:00
Update SDE and add the Windows version. Windows is sufficiently different from Linux that running tests under SDE for Windows, particularly with the new ABI tests, is worthwhile. Change-Id: I32c4f6de06b2e732ebb2c1492eb1766cae73c0e0 Reviewed-on: https://boringssl-review.googlesource.com/c/34064 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com>
2019-01-03 20:42:36 +00:00
The current revision is sde-external-8.16.0-2018-01-30-*.tar.bz2.
Switch to 64-bit tools on Windows. It's 2018. I'm not sure why I added the 32-bit ones; even the 32-bit bots build and run on 64-bit Windows. ninja.exe in depot_tools is also a 64-bit binary. I suspect this is because some of the depot_tools bits use --platform=win32, but that's just the sys.platform string. Alas, I stupidly named these "win32" way back. Dealing with the rename is probably more trouble than worth it right now since the build recipes refer to the name. Something to deal with later. (Regardless we'll want "win32" to point to 64-bit binaries so that try jobs can test it.) Also add the missing nasm-win32.exe to .gitignore. For some reason the 64-bit Yasm binary does not work on the vs2017 CQ bots, so I've left it alone. Hopefully it should be replaced by NASM later anyway. Change-Id: If65ececddbc6526ceebaafbef56eddea8ece58ba Reviewed-on: https://boringssl-review.googlesource.com/29384 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>
2018-06-26 22:08:56 +01:00
When adding new files, remember to update .gitignore.
Reference in New Issue Copy Permalink