mollyim/webrtc
1
0
Fork 0
mirror of https://github.com/mollyim/webrtc.git synced 2025-05-14 14:20:45 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
webrtc/tools_webrtc/mb
History
Edward Lemur 93bc308f31 MB: Add Android Perf (swarming) 
TBR=phoglund@webrtc.org

No-Try: true
Bug: chromium:755660
Change-Id: I9ff6304142bfd3b0ab4d2b1cfa46466685d58e09
Reviewed-on: https://webrtc-review.googlesource.com/14060
Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org>
Reviewed-by: Edward Lemur <ehmaldonado@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#20391}
2017-10-23 13:02:07 +00:00
..
docs Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
gn_isolate_map.pyl Reland "Make it possible to isolate bwe_simulations_tests" 2017-10-13 11:54:26 +00:00
mb Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
mb.bat Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
mb.py Update scripts to use DEPS-pinned depot_tools 2017-10-18 12:06:19 +00:00
mb_config.pyl MB: Add Android Perf (swarming) 2017-10-23 13:02:07 +00:00
mb_unittest.py Remove --target-devices-file 2017-10-09 09:17:17 +00:00
OWNERS Add phoglund@ to various OWNERS and remove kjellander@ 2017-10-19 09:21:12 +00:00
PRESUBMIT.py Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
README.md Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00

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:

  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: