Mirko Bonadei e93d109188 Add "Win asan 64-bit" in order to migrate away from the 2-bit version.
Chromium is thinking to remove the toolchain [1] and WebRTC can
probably switch to run it on x64 without any problem.

[1] - https://groups.google.com/a/chromium.org/d/msg/chromium-dev/IO5v9yx545M/H93qyx3UAgAJ

Bug: webrtc:10696
Change-Id: Ic5c6e795b662319a2338e4c3ff9e190874356296
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/139100
Reviewed-by: Oleh Prypin <oprypin@webrtc.org>
Reviewed-by: Artem Titarenko <artit@webrtc.org>
Commit-Queue: Oleh Prypin <oprypin@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#28118}
2019-05-31 07:57:13 +00:00
..
2017-05-09 06:30:13 +00:00
mb
2017-05-09 06:30:13 +00:00
2017-05-09 06:30:13 +00:00
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: