History

kjellander 957c1817b0 MB: Enable optimize_for_fuzzing=true for libfuzzer builds.

Build with this enabled since that's what Chromium bots do:
https://cs.chromium.org/chromium/src/build/config/compiler/BUILD.gn?rcl=0&l=89

BUG=chromium:677261
R=pbos@webrtc.org
NOTRY=True

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

2016-12-29 20:25:53 +00:00

docs

Move tools/mb -> tools-webrtc/mb

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

Move tools/mb -> tools-webrtc/mb

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

mb_config.pyl

MB: Enable optimize_for_fuzzing=true for libfuzzer builds.

2016-12-29 20:25:53 +00:00

mb_unittest.py

Move tools/mb -> tools-webrtc/mb

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

mb.bat

Move tools/mb -> tools-webrtc/mb

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

mb.py

Move tools/mb -> tools-webrtc/mb

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