| 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 117 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 128 You can pass the `-q/--quiet` flag to get mb to be silent unless there is an | 128 You can pass the `-q/--quiet` flag to get mb to be silent unless there is an |
| 129 error, and pass the `-v/--verbose` flag to get mb to log all of the files | 129 error, and pass the `-v/--verbose` flag to get mb to log all of the files |
| 130 that are read and written, and all the commands that are run. | 130 that are read and written, and all the commands that are run. |
| 131 | 131 |
| 132 If the build config will use the Goma distributed-build system, you can pass | 132 If the build config will use the Goma distributed-build system, you can pass |
| 133 the path to your Goma client in the `-g/--goma-dir` flag, and it will be | 133 the path to your Goma client in the `-g/--goma-dir` flag, and it will be |
| 134 incorporated into the appropriate flags for GYP or GN as needed. | 134 incorporated into the appropriate flags for GYP or GN as needed. |
| 135 | 135 |
| 136 If gen ends up using GYP, the path must have a valid GYP configuration as the | 136 If gen ends up using GYP, the path must have a valid GYP configuration as the |
| 137 last component of the path (i.e., specify `//out/Release_x64`, not `//out`). | 137 last component of the path (i.e., specify `//out/Release_x64`, not `//out`). |
| 138 The gyp script defaults to `//build/gyp_chromium`, but can be overridden with |
| 139 the `--gyp-script` flag, e.g. `--gyp-script=gypfiles/gyp_v8`. |
| 138 | 140 |
| 139 ### `mb help` | 141 ### `mb help` |
| 140 | 142 |
| 141 Produces help output on the other subcommands | 143 Produces help output on the other subcommands |
| 142 | 144 |
| 143 ### `mb lookup` | 145 ### `mb lookup` |
| 144 | 146 |
| 145 Prints what command will be run by `mb gen` (like `mb gen -n` but does | 147 Prints what command will be run by `mb gen` (like `mb gen -n` but does |
| 146 not require you to specify a path). | 148 not require you to specify a path). |
| 147 | 149 |
| (...skipping 131 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 279 run than you expect; running `'mb -v'` will print what it's doing and | 281 run than you expect; running `'mb -v'` will print what it's doing and |
| 280 run the commands; `'mb -n'` will print what it will do but *not* run | 282 run the commands; `'mb -n'` will print what it will do but *not* run |
| 281 the commands. | 283 the commands. |
| 282 | 284 |
| 283 If you hit weirder things than that, add some print statements to the | 285 If you hit weirder things than that, add some print statements to the |
| 284 python script, send a question to gn-dev@chromium.org, or | 286 python script, send a question to gn-dev@chromium.org, or |
| 285 [file a bug](https://crbug.com/new) with the label | 287 [file a bug](https://crbug.com/new) with the label |
| 286 'mb' and cc: dpranke@chromium.org. | 288 'mb' and cc: dpranke@chromium.org. |
| 287 | 289 |
| 288 | 290 |
| OLD | NEW |