blob: 9678a09fa0ea5a905a19d2fe9c88c620e4c33b28 [file] [log] [blame] [view]
dtrainorac84a372015-10-05 18:01:481# Running Blimp
2
3See [build](build.md) for instructions on how to build Blimp.
4
5## Running the client
6
7There are both Android and Linux clients. The Android client is the shipping
8client while the Linux client is used for development purposes.
9
10### Android Client
11
12Install the Blimp APK with the following:
13
14```bash
15./build/android/adb_install_apk.py $(PRODUCT_DIR)/apks/Blimp.apk
16```
17
18Set up any command line flags with:
19
20```bash
21./build/android/adb_blimp_command_line --enable-webgl
22```
23
24Run the Blimp APK with:
25
26```bash
27adb_run_blimp_client
28```
29
30### Linux Client
31
32TBD
maniscalco91be48c2015-10-05 19:30:2233
34## Running the engine
35
kmarshall6c98508d2016-01-11 21:06:2836### In a container
maniscalcoa4dae22c2015-10-05 20:13:5037For running the engine in a container, see [container](container.md).
kmarshall6c98508d2016-01-11 21:06:2838
39### On a workstation
40If you are running the engine on your workstation and are connected to the
41client device via USB, you'll need remote port forwarding to allow the Blimp
42client to talk to your computer. Follow the instructions
43[here](https://developer.chrome.com/devtools/docs/remote-debugging) to get
44started. You'll probably want to remap 25467 to "localhost:25467".
marcinjb446acf652016-01-15 22:18:3645
46### Required flags
47* `--blimp-client-token-path=$PATH`: Path to a file containing a nonempty
48token string. If this is not present, the engine will fail to boot.