OLD | NEW |
1 Mojo | 1 Mojo |
2 ==== | 2 ==== |
3 | 3 |
4 Mojo is an effort to extract a common platform out of Chrome's renderer and | 4 Mojo is an effort to extract a common platform out of Chrome's renderer and |
5 plugin processes that can support multiple types of sandboxed content, such as | 5 plugin processes that can support multiple types of sandboxed content, such as |
6 HTML, Pepper, or NaCl. | 6 HTML, Pepper, or NaCl. |
7 | 7 |
8 ## Set-up and code check-out | 8 ## Set-up and code check-out |
9 | 9 |
10 The instructions below only need to be done once. Note that a simple "git clone" | 10 The instructions below only need to be done once. Note that a simple "git clone" |
(...skipping 89 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
100 Run a demo: | 100 Run a demo: |
101 ``` | 101 ``` |
102 out/Debug/mojo_shell mojo:spinning_cube | 102 out/Debug/mojo_shell mojo:spinning_cube |
103 ``` | 103 ``` |
104 | 104 |
105 Run the tests: | 105 Run the tests: |
106 ``` | 106 ``` |
107 mojo/tools/mojob.py test | 107 mojo/tools/mojob.py test |
108 ``` | 108 ``` |
109 | 109 |
| 110 Run the benchmarks: |
| 111 ``` |
| 112 mojo/devtools/common/mojo_benchmark mojo/tools/data/benchmarks |
| 113 ``` |
| 114 |
110 Create a release build: | 115 Create a release build: |
111 ``` | 116 ``` |
112 mojo/tools/mojob.py gn --release | 117 mojo/tools/mojob.py gn --release |
113 mojo/tools/mojob.py build --release | 118 mojo/tools/mojob.py build --release |
114 mojo/tools/mojob.py test --release | 119 mojo/tools/mojob.py test --release |
115 ``` | 120 ``` |
116 | 121 |
117 ### Android | 122 ### Android |
118 | 123 |
119 To build for Android, first make sure that your checkout is [configured](#config
ure-android) to build | 124 To build for Android, first make sure that your checkout is [configured](#config
ure-android) to build |
(...skipping 162 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
282 for more detailed git instructions, including how to update your CL when you get | 287 for more detailed git instructions, including how to update your CL when you get |
283 review comments. There's a short tutorial that might be helpful to try before | 288 review comments. There's a short tutorial that might be helpful to try before |
284 making your first change: [C++ in Chromium | 289 making your first change: [C++ in Chromium |
285 101](http://dev.chromium.org/developers/cpp-in-chromium-101-codelab). | 290 101](http://dev.chromium.org/developers/cpp-in-chromium-101-codelab). |
286 | 291 |
287 To land a change after receiving LGTM: | 292 To land a change after receiving LGTM: |
288 ``` | 293 ``` |
289 $ git cl land | 294 $ git cl land |
290 ``` | 295 ``` |
291 | 296 |
292 Don't break the build! Waterfall is here: | 297 ## Monitoring |
293 http://build.chromium.org/p/client.mojo/waterfall | 298 |
| 299 Our [waterfall](http://build.chromium.org/p/client.mojo/waterfall) continuously |
| 300 builds and tests the code. Don't break the build! |
| 301 |
| 302 ### Benchmarks |
| 303 |
| 304 One of the bots, [Mojo Linux |
| 305 Perf](http://build.chromium.org/p/client.mojo/builders/Mojo%20Linux%20Perf) runs |
| 306 a [suite of benchmarks](mojo/tools/data/benchmarks) and uploads the results to |
| 307 the [performance dashboard](https://chromeperf.appspot.com/). You can browse the |
| 308 results [here](https://chromeperf.appspot.com/report), putting `mojo_benchmarks` |
| 309 as the "test suite". |
| 310 |
| 311 Automated alerts about performance regressions are sent to |
| 312 [mojo-perf-alerts@chromium.org](https://groups.google.com/a/chromium.org/forum/#
!forum/mojo-perf-alerts). |
| 313 |
| 314 For examples of interesting sets of graphs see: |
| 315 |
| 316 - [app |
| 317 startup](https://chromeperf.appspot.com/report?sid=4848464df5ca8467770d80b309
740ef56fbff00e773c2c53816fd8bff1fda1e0) |
| 318 - [ipc |
| 319 performance](https://chromeperf.appspot.com/report?sid=9abc20b46f6f8d908b0f07
847f1d42eab54c7025a098336e6dc2d3e2030d66f8) |
OLD | NEW |