I made two changes to video_quality_loopback_test to make it possible to run it on swarming. 1. We need to know the path to frame_analyzer when we're generating the build files, and it must be already present. I made frame_analyzer a resource, so it's downloaded to a known path before generating the build files. 2. The .zip files for apprtc and golang are downloaded and isolated. The script now extracts them and installs AppRTC. Passing task: https://chromium-swarm.appspot.com/task?id=3b230bcc04128210 Bug: chromium:755660 Change-Id: I34090897402421d5b7e29f21fbed354551197f92 Reviewed-on: https://webrtc-review.googlesource.com/40920 Reviewed-by: Patrik Höglund <phoglund@webrtc.org> Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21716}
MB - The Meta-Build wrapper
MB is a simple wrapper intended to provide a uniform interface to either GYP or GN, such that users and bots can call one script and not need to worry about whether a given bot is meant to use GN or GYP.
It supports two main functions:
-
"gen" - the main
gyp_chromium/gn geninvocation that generates the Ninja files needed for the build. -
"analyze" - the step that takes a list of modified files and a list of desired targets and reports which targets will need to be rebuilt.
We also use MB as a forcing function to collect all of the different
build configurations that we actually support for Chromium builds into
one place, in //tools/mb/mb_config.pyl.
For more information, see: