v8/tools/mb
Michael Achenbach 8b2e26945a [MB] Add fallback for MB configs on release branches
Bug: chromium:1136844
Change-Id: I635978a308eed2be33c1147f8007abb199bf195e
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3143998
Reviewed-by: Almothana Athamneh <almuthanna@chromium.org>
Reviewed-by: Liviu Rau <liviurau@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/main@{#76690}
2021-09-07 11:12:30 +00:00
..
docs Fixed typos 2019-01-08 07:31:02 +00:00
mb [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
mb_unittest.py remove swarming_client 2021-08-24 10:39:33 +00:00
mb.bat [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
mb.py [MB] Add fallback for MB configs on release branches 2021-09-07 11:12:30 +00:00
OWNERS [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
PRESUBMIT.py [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
README.md [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +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: