mirror of
https://github.com/mollyim/webrtc.git
synced 2025-05-17 07:37:51 +01:00
![]() Since the Perf tester is actually compiling histogram code, it needs to have it's own native OS gclient and GN config. The Builder has already built and cached the MacOS arm64 binaries to be tested for M1. I got confused and thought the tester was also compiling something for the bot it shards to. Bug: b/232347569 Change-Id: I0468945a04905d2d647626229af77c00d1f632fd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/263200 Reviewed-by: Jeremy Leconte <jleconte@google.com> Commit-Queue: Christoffer Jansson <jansson@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36969} |
||
---|---|---|
.. | ||
docs | ||
mb | ||
mb.bat | ||
mb.py | ||
mb_config.pyl | ||
mb_unittest.py | ||
OWNERS | ||
PRESUBMIT.py | ||
README.md |
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:
-
"gen" - the main
gyp_chromium
/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: