| commit | edbc860e1b978752d12a65cf6d0fb8b3e6b244da | [log] [tgz] |
|---|---|---|
| author | Jie Sheng <jiesheng@google.com> | Thu Jul 11 00:31:14 2024 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 11 01:09:04 2024 |
| tree | a6d0b0783ffbda976246aa9f3efd646850fc6e09 | |
| parent | 31e7b5378da92918055feccf90e3e03a8b4588b9 [diff] |
Update mb_config.pyl file for cros builders to gn args Migration in starlark. Bug: 347879500, 352093578 Change-Id: Ib009195ea901238535e03890c5a2d06345ff97b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5690927 Commit-Queue: Jie Sheng <jiesheng@google.com> Reviewed-by: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1325851} NOKEYCHECK=True GitOrigin-RevId: 77ef1ea5f55fee2f2d8ff74c91237e4c46352d97
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: