AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
13e07389ff
v8/tools/mb
History
Maxim Mazurok 58ef241d9e Fixed typos 
- "constuctor" -> "constructor"
- "dependendencies" -> "dependencies"
- "develpers" -> "developers"
- ["nonexistant"][1] -> ["nonexistent"][2]
- "reponsible" -> "responsible"

  [1]: https://en.wiktionary.org/wiki/nonexistant
  [2]: https://en.wiktionary.org/wiki/nonexistent

Change-Id: I8bb482d03c391bd0d37afd5d616229fa50a4ab77
Reviewed-on: https://chromium-review.googlesource.com/c/1390203
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Reviewed-by: Toon Verwaest <verwaest@chromium.org>
Reviewed-by: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: Michael Stanton <mvstanton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#58610}
2019-01-08 07:31:02 +00:00
..
docs Fixed typos 2019-01-08 07:31:02 +00:00
mb [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
mb_unittest.py [build] Used data deps from GN 2018-03-26 15:05:52 +00:00
mb.bat [mb] Copy MB from Chromium repo 2016-09-01 12:20:20 +00:00
mb.py Use gn from PATH on aix 2018-08-09 21:01:15 +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

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: