| commit | 60223ac1cfcff785fdc55ab13bd6e004c2da433a | [log] [tgz] |
|---|---|---|
| author | Jonathan Metzman <metzman@chromium.org> | Wed Apr 17 22:55:59 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Apr 17 22:55:59 2019 |
| tree | f2da1f4760b72655c1a3b8d1f0fca14d2a58e647 | |
| parent | 89489b870249ee14f9716257c4d89d4abb8ee49e [diff] |
Reland "Don't build seed corpora in most configs and delete duplicated config" This is a reland of 3b8a3ffc8ee941944e3cc13ac5bf63b167cfcc06 Original change's description: > Don't build seed corpora in most configs and delete duplicated config > > Only build seed corpora where it is necessary, in order to reduce > build sizes. > > Bug: 952412 > Change-Id: I6e529226d4ba51fd547c1869525a9f094fdcd998 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566454 > Reviewed-by: Max Moroz <mmoroz@chromium.org> > Reviewed-by: Ben Pastene <bpastene@chromium.org> > Commit-Queue: Jonathan Metzman <metzman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#650506} Bug: 952412 Change-Id: I0ce44fb063784db1d7e4215fb69868cbe6e5e9ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572639 Commit-Queue: Jonathan Metzman <metzman@chromium.org> Reviewed-by: Dirk Pranke <dpranke@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#651938} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 30dbf99d2683730f995c4315acd02233b349fd29
MB is a simple wrapper around the GN build tool.
It was originally written as part of the GYP->GN migration, in order 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 was meant to use GN or GYP.
It eventually grew additional functionality and is now still used even though everything is GN-only.
It supports two main functions:
“gen” - the main 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: