v8/tools/mb
Michael Achenbach 41d9e85714 [build] Update MB fork with upstream changes
This updates the V8 side MB fork with all upstream changes until:
https://chromium.googlesource.com/chromium/src/+/f4d92a15f/tools/mb/mb.py

This includes a required feature for mapping isolate targets to
runtime deps.

Bug: chromium:669910
Change-Id: I22244455b22737cfbfc45adef93581ef44cf4151
Reviewed-on: https://chromium-review.googlesource.com/778879
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#49487}
2017-11-20 12:29:12 +00:00
..
docs [build] Update MB fork with upstream changes 2017-11-20 12:29:12 +00:00
mb [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
mb_unittest.py [build] Update MB fork with upstream changes 2017-11-20 12:29:12 +00:00
mb.bat [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
mb.py [build] Update MB fork with upstream changes 2017-11-20 12:29:12 +00:00
OWNERS [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
PRESUBMIT.py [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
README.md [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00

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: