OLD | NEW |
1 # Running Blimp | 1 # Running Blimp |
2 | 2 |
3 See [build](build.md) for instructions on how to build Blimp. | 3 See [build](build.md) for instructions on how to build Blimp. |
4 | 4 |
5 ## Running the client | 5 ## Running the client |
6 | 6 |
7 There are both Android and Linux clients. The Android client is the shipping | 7 There are both Android and Linux clients. The Android client is the shipping |
8 client while the Linux client is used for development purposes. | 8 client while the Linux client is used for development purposes. |
9 | 9 |
10 ### Android Client | 10 ### Android Client |
(...skipping 82 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
93 ./build/android/adb_reverse_forwarder.py --debug -v 25467 25467 | 93 ./build/android/adb_reverse_forwarder.py --debug -v 25467 25467 |
94 ``` | 94 ``` |
95 | 95 |
96 ### Required engine binary flags | 96 ### Required engine binary flags |
97 * `--blimp-client-token-path=$PATH`: Path to a file containing a nonempty | 97 * `--blimp-client-token-path=$PATH`: Path to a file containing a nonempty |
98 token string. If this is not present, the engine will fail to boot. | 98 token string. If this is not present, the engine will fail to boot. |
99 * `--use-remote-compositing`: Ensures that the renderer uses the remote | 99 * `--use-remote-compositing`: Ensures that the renderer uses the remote |
100 compositor. | 100 compositor. |
101 * `--disable-cached-picture-raster`: Ensures that rasterized content is not | 101 * `--disable-cached-picture-raster`: Ensures that rasterized content is not |
102 destroyed before serialization. | 102 destroyed before serialization. |
103 * `--android-fonts-path=$PATH`: Path to where the fonts are located. | |
104 Typically this would be `out-linux/Debug/gen/third_party/blimp_fonts`. | |
105 | 103 |
106 #### Typical invocation | 104 #### Typical invocation |
107 When the client connects to a manually specified engine instead of using the | 105 When the client connects to a manually specified engine instead of using the |
108 assigner, it will use a dummy token. The engine needs to know what this token | 106 assigner, it will use a dummy token. The engine needs to know what this token |
109 is, so it must be provided using the `--blimp-client-token-path` flag. The token | 107 is, so it must be provided using the `--blimp-client-token-path` flag. The token |
110 is available in the constant `kDummyClientToken` in | 108 is available in the constant `kDummyClientToken` in |
111 `blimp/client/session/assignment_source.h`. You can easily store that to a file | 109 `blimp/client/session/assignment_source.h`. You can easily store that to a file |
112 by running the following command once: | 110 by running the following command once: |
113 | 111 |
114 ```bash | 112 ```bash |
115 awk '{if ( match($0, /^\s*const char kDummyClientToken.*/) ) { print substr($5,
2, length($5)-3);} }' \ | 113 awk '{if ( match($0, /^\s*const char kDummyClientToken.*/) ) { print substr($5,
2, length($5)-3);} }' \ |
116 ./blimp/client/session/assignment_source.h > /tmp/blimpengine-token | 114 ./blimp/client/session/assignment_source.h > /tmp/blimpengine-token |
117 ``` | 115 ``` |
118 | 116 |
119 Then start the engine using these flags: | 117 Then start the engine using these flags: |
120 | 118 |
121 ```bash | 119 ```bash |
122 out-linux/Debug/blimp_engine_app \ | 120 out-linux/Debug/blimp_engine_app \ |
123 --use-remote-compositing \ | 121 --use-remote-compositing \ |
124 --disable-cached-picture-raster \ | 122 --disable-cached-picture-raster \ |
125 --blimp-client-token-path=/tmp/blimpengine-token \ | 123 --blimp-client-token-path=/tmp/blimpengine-token \ |
126 --user-data-dir=/tmp/blimpengine \ | 124 --user-data-dir=/tmp/blimpengine \ |
127 --android-fonts-path=out-linux/Debug/gen/third_party/blimp_fonts \ | |
128 --enable-logging=stderr \ | 125 --enable-logging=stderr \ |
129 --vmodule="blimp*=1" | 126 --vmodule="blimp*=1" |
130 ``` | 127 ``` |
OLD | NEW |