Lines Matching full:mb

1 # The MB (Meta-Build wrapper) user guide
7 `mb` is a simple python wrapper around the GYP and GN meta-build tools to
17 For more discussion of MB, see also [the design spec](design_spec.md).
19 ## MB subcommands
21 ### `mb analyze`
23 `mb analyze` is reponsible for determining what targets are affected by
27 mb analyze -c chromium_linux_rel //out/Release input.json output.json
31 flags must be specified so that `mb` can figure out which config to use.
60 The third positional argument is a (normal) path to where mb will write
94 `-q/--quiet`, and `-v/--verbose` flags work as documented for `mb gen`.
96 ### `mb audit`
98 `mb audit` is used to track the progress of the GYP->GN migration. You can
101 See `mb help audit` for more details (most people are not expected to care
104 ### `mb gen`
106 `mb gen` is responsible for generating the Ninja files by invoking either GYP
111 % mb gen -m tryserver.chromium.linux -b linux_rel //out/Release
112 % mb gen -c linux_rel_trybot //out/Release
116 flags must be specified so that `mb` can figure out which config to use. The
120 By default, MB will look for a bot config file under `//ios/build/bots` (see
123 `//tools/mb/mb_config.pyl` to look up the config information, but you can
128 You can pass the `-n/--dryrun` flag to mb gen to see what will happen without
131 You can pass the `-q/--quiet` flag to get mb to be silent unless there is an
132 error, and pass the `-v/--verbose` flag to get mb to log all of the files
144 ### `mb help`
148 ### `mb lookup`
150 Prints what command will be run by `mb gen` (like `mb gen -n` but does
155 `mb gen`.
157 ### `mb validate`
166 `mb gen`.
173 `mb gen` is also responsible for generating the `.isolate` and
177 If you wish to generate the isolate files, pass `mb gen` the
183 MB will take this file, translate each build target to the matching GN
188 Once GN has computed the lists of runtime dependencies, MB will then
190 in [mb.py](https://code.google.com/p/chromium/codesearch?q=mb.py#chromium/src/tools/mb/mb.py&q=mb.p…
236 When `mb gen` or `mb analyze` executes, it takes a config name, looks it
277 and you ran `mb gen -c linux_release_trybot //out/Release`, it would
281 (From that you can see that mb is intentionally dumb and does not
284 ## Debugging MB
286 By design, MB should be simple enough that very little can go wrong.
289 run than you expect; running `'mb -v'` will print what it's doing and
290 run the commands; `'mb -n'` will print what it will do but *not* run
296 'mb' and cc: dpranke@chromium.org.