bd33ce2620
This is a reland of 642a49d1eb20b8c5744e745de79ddb585e0f7472 The change has the same effect but is now implemented through mb, rather than specifying a 'script', so that Android's special handling is not skipped. Original change's description: > Add wrapper to normalize flags. > > Bug: None > Change-Id: I9d43602cc66198a29dbc0e7586d948ee76c5ec84 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/145204 > Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: Oleh Prypin <oprypin@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#28532} Bug: webrtc:10616 Change-Id: I60ebd4891dbe8de18c653f8af88181ea966307de Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/145409 Commit-Queue: Oleh Prypin <oprypin@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28572}
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: