webrtc/tools_webrtc/mb
Mirko Bonadei 910540d55a Explicitly setting use_lld=false on MSVC bots.
In order to unblock the Chromium Roll, WebRTC should set use_lld=false
when MSVC is used (as discussed here [1]).

[1] - https://chromium-review.googlesource.com/c/chromium/src/+/1092611

Bug: None
Change-Id: Ia052d3d8842871c3051fe36991396976f5839f4c
Reviewed-on: https://webrtc-review.googlesource.com/83102
Reviewed-by: Patrik Höglund <phoglund@webrtc.org>
Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#23582}
2018-06-12 13:49:38 +00:00
..
docs Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
gn_isolate_map.pyl Reland "Add support for launching webcam software for use in recipes" 2018-05-17 11:42:21 +00:00
mb Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
mb.bat Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
mb.py Allow mixing gtest and non-gtest args in gtest-parallel-wrapper 2018-05-23 14:19:20 +00:00
mb_config.pyl Explicitly setting use_lld=false on MSVC bots. 2018-06-12 13:49:38 +00:00
mb_unittest.py Allow mixing gtest and non-gtest args in gtest-parallel-wrapper 2018-05-23 14:19:20 +00:00
OWNERS Add phoglund@ to various OWNERS and remove kjellander@ 2017-10-19 09:21:12 +00:00
PRESUBMIT.py Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
README.md Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +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: