| commit | e244ccaa70aeedf5a460576fe7f0d5f253dd483d | [log] [tgz] |
|---|---|---|
| author | Struan Shrimpton <sshrimp@google.com> | Tue May 24 00:00:15 2022 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 24 00:23:52 2022 |
| tree | 1eefe3b86df91a136c355baf3aa7a692e90814e3 | |
| parent | 34a9fd4984fb1a8e9ed8cce6062d7807e9f81498 [diff] |
[infra] Remove use-st arg from mb and filter files for removed buidler Since the stable test builders were removed and this experiment has evolved there's no need for this argument in the recipe. A similar one for the rts-ml that will follow (for mb.py) Change-Id: Iabd3f92a64ec2277d1518a084708b9ace8c38da2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3661446 Reviewed-by: Gregory Guterman <guterman@google.com> Commit-Queue: Struan Shrimpton <sshrimp@google.com> Cr-Commit-Position: refs/heads/main@{#1006670} NOKEYCHECK=True GitOrigin-RevId: 88eb34c4b8d989c38a7475a9f42778403b453396
MB is a simple wrapper around the GN build tool.
It was originally written as part of the GYP->GN migration, in order 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 was meant to use GN or GYP.
It eventually grew additional functionality and is now still used even though everything is GN-only.
It supports two main functions:
“gen” - the main gn gen invocation 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: