852ca318a1
'windk' is no longer a thing. There are two separate variables to point at your compiler (win_vc), and SDK (win_sdk). 'msvc' is no longer a thing, either. By default, we look for 2017 and then 2015 (in the default locations). If neither is located, use an assert to let users know they should set win_vc. Then, detect if win_vc points at a 2017 or 2015 installation, and configure it automatically. Because the toolchain is now 2017, update the GN files to handle building x86 in that configuration. In fact, we only support x86 builds (with 2017 or 2015) using the toolchain assets. Keep a 2015 toolchain around as a new asset, so we can add bot coverage. Docs-Preview: https://skia.org/?cl=81841 Bug: skia: Change-Id: I8c68a6f949e54c0e798a219450bbb9406f8dc6ac Reviewed-on: https://skia-review.googlesource.com/81841 Reviewed-by: Mike Klein <mtklein@chromium.org> Commit-Queue: Brian Osman <brianosman@google.com> |
||
---|---|---|
.. | ||
android_ndk_darwin | ||
android_ndk_linux | ||
android_ndk_windows | ||
android_sdk | ||
armhf_sysroot | ||
cast_toolchain | ||
chromebook_arm_gles | ||
chromebook_x86_64_gles | ||
clang_linux | ||
clang_win | ||
emscripten_sdk | ||
go | ||
linux_vulkan_intel_driver_debug | ||
linux_vulkan_intel_driver_release | ||
linux_vulkan_sdk | ||
protoc | ||
scripts | ||
skimage | ||
skp | ||
svg | ||
valgrind | ||
win_toolchain | ||
win_toolchain_2015 | ||
win_vulkan_sdk | ||
__init__.py | ||
asset_utils_test.py | ||
asset_utils.py | ||
assets.py | ||
README.md |
Assets
This directory contains tooling for managing assets used by the bots. The primary entry point is assets.py, which allows a user to add, remove, upload, and download assets.
Assets are stored in Google Storage, named for their version number.
Individual Assets
Each asset has its own subdirectory with the following contents:
- VERSION: The current version number of the asset.
- download.py: Convenience script for downloading the current version of the asset.
- upload.py: Convenience script for uploading a new version of the asset.
- [optional] create.py: Script which creates the asset, implemented by the user.
- [optional] create_and_upload.py: Convenience script which combines create.py with upload.py.
Examples
Add a new asset and upload an initial version.
$ infra/bots/assets/assets.py add myasset
Creating asset in infra/bots/assets/myasset
Creating infra/bots/assets/myasset/download.py
Creating infra/bots/assets/myasset/upload.py
Creating infra/bots/assets/myasset/common.py
Add script to automate creation of this asset? (y/n) n
$ infra/bots/assets/myasset/upload.py -t ${MY_ASSET_LOCATION}
$ git commit
Add an asset whose creation can be automated.
$ infra/bots/assets/assets.py add myasset
Add script to automate creation of this asset? (y/n) y
$ vi infra/bots/assets/myasset/create.py
(implement the create_asset function)
$ infra/bots/assets/myasset/create_and_upload.py
$ git commit