b2d5577caf
In addition to moving tools/mb -> tools-webrtc/mb, also move webrtc/build/mb_config.pyl into tools-webrtc/mb to match the default location better. Remove Chromium-specific check for 'mb validate' that failed due to doing this (we never cleaned that when we forked the code). BUG=webrtc:5006 TBR=ehmaldonado@webrtc.org NOTRY=True TESTED=Manually ran: tools-webrtc/mb/mb.py gen -m client.webrtc -b 'iOS64 Release' --config-file tools-webrtc/mb/mb_config.pyl //out/Release-iphoneos tools-webrtc/mb/mb.py gen -m client.webrtc -b 'Mac64 Release' --config-file tools-webrtc/mb/mb_config.pyl //out/Release-mac Review-Url: https://codereview.webrtc.org/2585743002 . Cr-Commit-Position: refs/heads/master@{#15664}
23 lines
820 B
Markdown
23 lines
820 B
Markdown
# 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:
|
|
|
|
* [The User Guide](docs/user_guide.md)
|
|
* [The Design Spec](docs/design_spec.md)
|