AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
50a91fe9ee
v8/tools/mb
History
Michael Achenbach 1cd6fd9ff8 [build] Drop Chromium-specific features from V8's MB fork 
V8 passes the command explicitly to each swarming task, hence it's
not necessary to store the command in the isolate.

This drops the Chromium-specific code in MB that creates the
swarming command based on Chromium test features.

This also makes the swarming targets option a no-op to allow
activating it on the infra side without disruption.

Bug: chromium:669910
Change-Id: I6cb03f05d034092a25d879d52b4d64952493f55b
Reviewed-on: https://chromium-review.googlesource.com/779148
Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#49520}
2017-11-21 10:25:19 +00:00
..
docs [build] Update MB fork with upstream changes 2017-11-20 12:29:12 +00:00
mb
mb_unittest.py [build] Drop Chromium-specific features from V8's MB fork 2017-11-21 10:25:19 +00:00
mb.bat
mb.py [build] Drop Chromium-specific features from V8's MB fork 2017-11-21 10:25:19 +00:00
OWNERS
PRESUBMIT.py
README.md

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: