mirror of
https://chromium.googlesource.com/libyuv/libyuv
synced 2025-12-07 01:06:46 +08:00
33503d9c9c
This includes:
- fixing a handrolled raw exec-based DEPS parser that was failing
to parse Str, similar to crbug.com/1106435.
- rolling chromium forward by nearly a year. (The last roll that
landed was crrev.com/c/1797295). This required a bunch of changes in
order to be able to successfully sync, run gn, and compile:
- switching the mirrors for three repositories to match chromium,
which switched in crrev.com/c/2062580.
- making libyuv write an empty gclient_args file
- adding a few build_override gn arguments
- adding nasm as a deps entry, as it's now required by libjpeg_turbo
- android:
- adding jdk, libunwindstack, and turbine
- rolling the android sdk
- rolling bazel and r8
- rolling the cipd packages managed by third_party/android_deps
- adding six and requests to .vpython for the test runner
- switching to memcpy in a few places to avoid SIGBUS errors on
arm due to unaligned reads
- linux:
- checking out instrumented libraries for msan (including adding
depot_tools to deps for the hook)
- mac:
- adding mac_xcode_version to gclient_gn_args
- win:
- limit mac_toolchain to checkout_mac
Bug: 1063768, 1097306
Change-Id: Idd86fffcdac174fd2f7899243a56af4f1ed8077e
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/2384320
Reviewed-by: Frank Barchard <fbarchard@chromium.org>
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
60 lines
1.8 KiB
Plaintext
60 lines
1.8 KiB
Plaintext
# This is a vpython "spec" file.
|
|
#
|
|
# It describes patterns for python wheel dependencies of the python scripts in
|
|
# the chromium repo, particularly for dependencies that have compiled components
|
|
# (since pure-python dependencies can be easily vendored into third_party).
|
|
#
|
|
# When vpython is invoked, it finds this file and builds a python VirtualEnv,
|
|
# containing all of the dependencies described in this file, fetching them from
|
|
# CIPD (the "Chrome Infrastructure Package Deployer" service). Unlike `pip`,
|
|
# this never requires the end-user machine to have a working python extension
|
|
# compilation environment. All of these packages are built using:
|
|
# https://chromium.googlesource.com/infra/infra/+/master/infra/tools/dockerbuild/
|
|
#
|
|
# All python scripts in the repo share this same spec, to avoid dependency
|
|
# fragmentation.
|
|
#
|
|
# If you have depot_tools installed in your $PATH, you can invoke python scripts
|
|
# in this repo by running them as you normally would run them, except
|
|
# substituting `vpython` instead of `python` on the command line, e.g.:
|
|
# vpython path/to/script.py some --arguments
|
|
#
|
|
# Read more about `vpython` and how to modify this file here:
|
|
# https://chromium.googlesource.com/infra/infra/+/master/doc/users/vpython.md
|
|
|
|
python_version: "2.7"
|
|
|
|
# Used by:
|
|
# third_party/catapult
|
|
wheel: <
|
|
name: "infra/python/wheels/psutil/${platform}_${py_python}_${py_abi}"
|
|
version: "version:5.2.2"
|
|
>
|
|
|
|
# Used by:
|
|
# third_party/catapult
|
|
wheel: <
|
|
name: "infra/python/wheels/pypiwin32/${vpython_platform}"
|
|
version: "version:219"
|
|
match_tag: <
|
|
platform: "win32"
|
|
>
|
|
match_tag: <
|
|
platform: "win_amd64"
|
|
>
|
|
>
|
|
|
|
# Used by:
|
|
# tools/swarming_client
|
|
wheel: <
|
|
name: "infra/python/wheels/six-py2_py3"
|
|
version: "version:1.15.0"
|
|
>
|
|
|
|
# Used by:
|
|
# build/android
|
|
wheel: <
|
|
name: "infra/python/wheels/requests-py2_py3"
|
|
version: "version:2.13.0"
|
|
>
|