History

kjellander 73f01de4ed iOS: Use JSON for GN configuration instead of MB + remove symbols.

This aligns with how the ios recipe module is used in Chromium.
It should prevent breakages like one we had recently.

It also means we're no longer setting symbol_level=1 explicitly.
The default is 0 (no symbols), which is now what's being used.

Also move all the directories containing JSON files into
tools-webrtc/ios/bots to make it clearer (and more similar to
Chromium).

BUG=webrtc:7140, webrtc:7161
NOTRY=True

Review-Url: https://codereview.webrtc.org/2688103002
Cr-Commit-Position: refs/heads/master@{#16633}

2017-02-15 20:34:03 +00:00

docs

Move tools/mb -> tools-webrtc/mb

2016-12-18 21:14:50 +00:00

gn_isolate_map.pyl

Moving gn_isolate_map.pyl to tools-webrtc/mb

2017-01-25 08:36:50 +00:00

Move tools/mb -> tools-webrtc/mb

2016-12-18 21:14:50 +00:00

mb_config.pyl

iOS: Use JSON for GN configuration instead of MB + remove symbols.

2017-02-15 20:34:03 +00:00

mb_unittest.py

iOS: Use JSON for GN configuration instead of MB + remove symbols.

2017-02-15 20:34:03 +00:00

mb.bat

Move tools/mb -> tools-webrtc/mb

2016-12-18 21:14:50 +00:00

mb.py

iOS: Use JSON for GN configuration instead of MB + remove symbols.

2017-02-15 20:34:03 +00:00

OWNERS

Move tools/mb -> tools-webrtc/mb

2016-12-18 21:14:50 +00:00

PRESUBMIT.py

Move tools/mb -> tools-webrtc/mb

2016-12-18 21:14:50 +00:00

README.md

Move tools/mb -> tools-webrtc/mb

2016-12-18 21:14:50 +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:

"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: