This is a reland of 7a73c772e21983857e46cb4fcedc6cfa3f42c03e The change to fix the downstream issue is just the switch from "test" to "rtc_test" which is a GN template that expands to "test". Original change's description: > Switch from "rtc_ios_xctest_test" to "test". > > Using the "test" GN template instead of the "ios_xctest_test" one we > will get iOS support for isolates via MB and GN for free, making it > easier to migrate the iOS recipe and fix bugs.webrtc.org/11604. > > Bug: webrtc:11881 > Change-Id: I72b90f8494c473fa567e6296caf7a771e4caba92 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/182680 > Reviewed-by: Dirk Pranke <dpranke@google.com> > Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#32064} Bug: webrtc:11881 Change-Id: Ia5338859f4e893b9f19bcca6b26b8cf66d5984e8 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/183766 Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/master@{#32075}
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: