09d90147fb
Nothing is different from the original change. The original change was reverted because it was thought it might have caused an outage for the windows bots. (It didn't.) This is a reland of 28addd03c1040fc5a634ed92a7edde2aea811e79 Original change's description: > Make it possible to isolate bwe_simulations_tests > > Add missing data dependencies and add it to gn_isolate_map.pyl > > Bug: chromium:749648 > Change-Id: I6b6c1bb2e4d647471a2747042788a691ce2e1e5d > Reviewed-on: https://webrtc-review.googlesource.com/8721 > Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org> > Reviewed-by: Henrik Kjellander <kjellander@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#20258} Bug: chromium:749648 No-Try: true Change-Id: I5531c5f8b58e0d5b8b6ceeea90acb4bd8e6e6e4f Reviewed-on: https://webrtc-review.googlesource.com/9320 Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org> Reviewed-by: Edward Lemur <ehmaldonado@webrtc.org> Reviewed-by: Henrik Kjellander <kjellander@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20280}
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 geninvocation 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: