Jeremy Leconte 55c55c3c43 Reorder mb_config.pyl to fix 'mb.py validate'
This is a follow up of this CL: https://crrev.com/c/3611486.

Bug: b/231404336
Change-Id: I3b6f4b780aa1939b6b2d0f1d08d1746a3a6f86dc
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/261080
Commit-Queue: Jeremy Leconte <jleconte@google.com>
Reviewed-by: Christoffer Jansson <jansson@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#36752}
2022-05-04 08:31:29 +00:00
..
2021-07-30 13:47:50 +00:00
mb
2017-05-09 06:30:13 +00:00
2022-04-19 12:24:26 +00:00
2020-03-09 14:08:30 +00:00
2017-05-09 06:30:13 +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: