| OLD | NEW |
| 1 # The MB (Meta-Build wrapper) user guide | 1 # The MB (Meta-Build wrapper) user guide |
| 2 | 2 |
| 3 [TOC] | 3 [TOC] |
| 4 | 4 |
| 5 ## Introduction | 5 ## Introduction |
| 6 | 6 |
| 7 `mb` is a simple python wrapper around the GYP and GN meta-build tools to | 7 `mb` is a simple python wrapper around the GYP and GN meta-build tools to |
| 8 be used as part of the GYP->GN migration. | 8 be used as part of the GYP->GN migration. |
| 9 | 9 |
| 10 It is intended to be used by bots to make it easier to manage the configuration | 10 It is intended to be used by bots to make it easier to manage the configuration |
| (...skipping 89 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 100 a directory, then runs GYP or GN as appropriate: | 100 a directory, then runs GYP or GN as appropriate: |
| 101 | 101 |
| 102 ``` | 102 ``` |
| 103 % mb gen -m tryserver.chromium.linux -b linux_rel //out/Release | 103 % mb gen -m tryserver.chromium.linux -b linux_rel //out/Release |
| 104 % mb gen -c linux_rel_trybot //out/Release | 104 % mb gen -c linux_rel_trybot //out/Release |
| 105 ``` | 105 ``` |
| 106 | 106 |
| 107 Either the `-c/--config` flag or the `-m/--master` and `-b/--builder` flags | 107 Either the `-c/--config` flag or the `-m/--master` and `-b/--builder` flags |
| 108 must be specified so that `mb` can figure out which config to use. | 108 must be specified so that `mb` can figure out which config to use. |
| 109 | 109 |
| 110 By default, MB will look in `//tools/mb/mb_config.pyl` to look up the config | 110 By default, MB will look for a bot config file under `//ios/build/bots` (see |
| 111 information, but you can specify a custom config file using the | 111 [design_spec.md](the design spec) for details of how the bot config files |
| 112 `-f/--config-file` flag. | 112 work). If no matching one is found, will then look in |
| 113 `//tools/mb/mb_config.pyl` to look up the config information, but you can |
| 114 specify a custom config file using the `-f/--config-file` flag. |
| 113 | 115 |
| 114 The path must be a GN-style "source-absolute" path (as above). | 116 The path must be a GN-style "source-absolute" path (as above). |
| 115 | 117 |
| 116 You can pass the `-n/--dryrun` flag to mb gen to see what will happen without | 118 You can pass the `-n/--dryrun` flag to mb gen to see what will happen without |
| 117 actually writing anything. | 119 actually writing anything. |
| 118 | 120 |
| 119 You can pass the `-q/--quiet` flag to get mb to be silent unless there is an | 121 You can pass the `-q/--quiet` flag to get mb to be silent unless there is an |
| 120 error, and pass the `-v/--verbose` flag to get mb to log all of the files | 122 error, and pass the `-v/--verbose` flag to get mb to log all of the files |
| 121 that are read and written, and all the commands that are run. | 123 that are read and written, and all the commands that are run. |
| 122 | 124 |
| (...skipping 147 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 270 run than you expect; running `'mb -v'` will print what it's doing and | 272 run than you expect; running `'mb -v'` will print what it's doing and |
| 271 run the commands; `'mb -n'` will print what it will do but *not* run | 273 run the commands; `'mb -n'` will print what it will do but *not* run |
| 272 the commands. | 274 the commands. |
| 273 | 275 |
| 274 If you hit weirder things than that, add some print statements to the | 276 If you hit weirder things than that, add some print statements to the |
| 275 python script, send a question to gn-dev@chromium.org, or | 277 python script, send a question to gn-dev@chromium.org, or |
| 276 [file a bug](https://crbug.com/new) with the label | 278 [file a bug](https://crbug.com/new) with the label |
| 277 'mb' and cc: dpranke@chromium.org. | 279 'mb' and cc: dpranke@chromium.org. |
| 278 | 280 |
| 279 | 281 |
| OLD | NEW |