commit | 43f13a9556e02f1bc63013770c1ec37e53844fc3 | [log] [tgz] |
---|---|---|
author | Rahul Kumar Adudodla <adudodla@google.com> | Sat May 28 04:42:55 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Sat May 28 05:01:58 2022 |
tree | e61de4f2e9fd2eeed5fd5bd4b926c2b2804ef550 | |
parent | 45f036439d799e323a9daf2aa6a035e301501535 [diff] |
add ios-asan to chromium.memory group This is part of moving ios-asan form chromium.fyi to chromium.memory Bug: 1249192 Change-Id: Ia118ef8790af43c10778a8e4bcc27f170dce60b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3673110 Reviewed-by: Stephanie Kim <kimstephanie@google.com> Commit-Queue: Rahul Kumar Adudodla <adudodla@google.com> Cr-Commit-Position: refs/heads/main@{#1008547} NOKEYCHECK=True GitOrigin-RevId: 133c428bfa1289484841d69e1ca92015daf2b0db
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: