d15f3e1220
The flags isolated-script-test-output and isolated-script-test-perf-output need to be consumed by the tests. The generated .app folder in added in the data list of the gni file. This will make it available in the runtime_deps file and thus will be populated to the swarming tasks. Bug: webrtc:13556 Change-Id: I2c75774b847d9f686c3abc00ba0400bbc3fcefae Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/240520 Reviewed-by: Artem Titov <titovartem@webrtc.org> Reviewed-by: Christoffer Jansson <jansson@google.com> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Jeremy Leconte <jleconte@google.com> Cr-Commit-Position: refs/heads/main@{#36029}
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: