Jeremy Leconte aa0d4061ba Reland "Make tools_webrtc/mb inherit from tools/mb."
This is a reland of commit 7a324b977c5ab6f9b88bcce3353feade943ccefe

Original change's description:
> Make tools_webrtc/mb inherit from tools/mb.
>
> Bug: webrtc:13867
> Change-Id: I33e998d260454d16120b09fedecf0c25d2654611
> Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/256809
> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
> Commit-Queue: Jeremy Leconte <jleconte@google.com>
> Cr-Commit-Position: refs/heads/main@{#36347}

Bug: webrtc:13867
Change-Id: I8fe4424771876ea725f5c9a3c5d13b2f6ad83917
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/256970
Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
Commit-Queue: Jeremy Leconte <jleconte@google.com>
Cr-Commit-Position: refs/heads/main@{#36361}
2022-03-29 07:02:40 +00:00
..
2021-07-30 13:47:50 +00:00
mb
2020-03-09 14:08:30 +00:00

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:

  1. "gen" - the main gyp_chromium / gn gen invocation that generates the Ninja files needed for the build.

  2. "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: