Doc updates from reading through them.
Changes:
* clang is now used on Android
* Remove GYP mentions
Delete obsolete:
* common_build_tasks.md (all about GYP)
* shift_based_development.md (a git workflow, nothing chromium-specific)
Change-Id: I9ee75395bbe8f29ce4f856b14fbeff330d6b2c13
Reviewed-on: https://chromium-review.googlesource.com/679054
Reviewed-by: Eric Stevenson <[email protected]>
Commit-Queue: Andrew Grieve <[email protected]>
Cr-Commit-Position: refs/heads/master@{#503807}diff --git a/docs/working_remotely_with_android.md b/docs/working_remotely_with_android.md
index f804fc6..eb98447 100644
--- a/docs/working_remotely_with_android.md
+++ b/docs/working_remotely_with_android.md
@@ -5,12 +5,6 @@
## Introduction
-When you call /build/android/run_tests.py or
-/build/android/run_instrumentation_tests.py it assumes an Android device
-is attached to the local host.
-
-TODO: these scripts do not exist.
-
If you want to work remotely from your laptop with an Android device attached to
it, while keeping an ssh connection to a remote desktop machine where you have
your build environment setup, you will have to use one of the two alternatives
@@ -18,19 +12,6 @@
## Option 1: SSHFS - Mounting the out/Debug directory
-### On your remote host machine
-
-You can open a regular ssh to your host.
-
- # build it
- desktop$ cd $SRC;
- desktop$ . build/android/envsetup.sh
- desktop$ build/gyp_chromium -DOS=android
- desktop$ ninja -C out/Debug
-
-See also
-[Android Build Instructions](https://www.chromium.org/developers/how-tos/android-build-instructions).
-
### On your laptop
You have to have an Android device attached to it.
@@ -52,13 +33,9 @@
laptop$ adb devices
laptop$ adb root
-# Install APK (which was previously built in the host machine).
-
-laptop$ python build/android/adb_install_apk.py --apk ContentShell.apk --apk_package org.chromium.content_shell
-
# Run tests.
-laptop$ python build/android/run_instrumentation_tests.py -I --test-apk ContentShellTest -vvv
+laptop$ out/Default/bin/run_$YOUR_TEST
```
*** note
@@ -76,14 +53,11 @@
# Rebuild the needed binaries on your laptop.
-laptop$ build/gyp_chromium -DOS=android
laptop$ ninja -C out/Debug md5sum host_forwarder
```
## Option 2: SSH Tunneling
-### Option 2a: Use a script
-
Copy /tools/android/adb_remote_setup.sh to your laptop, then run it.
adb_remote_setup.sh updates itself, so you only need to copy it once.
@@ -93,29 +67,8 @@
laptop$ ./adb_remote_setup.sh <desktop_hostname> <path_to_adb_on_desktop>
```
-### Option 2b: Manual tunneling
-
-You have to make sure that ports 5037, 10000, ad 10201 are not being used on
-either your laptop or your desktop. Try the command: `netstat -nap | grep 10000`
-to see
-
-Kill the pids that are using those ports.
-
-#### On your host machine
+### On your host machine
```shell
-desktop$ killall adb
-desktop$ killall host_forwarder
-```
-
-#### On your laptop
-
-```shell
-laptop$ ssh -C -R 5037:localhost:5037 -R 10000:localhost:10000 -R 10201:localhost:10201 <desktop_host_name>
-```
-
-#### On your host machine
-
-```shell
-desktop$ python build/android/run_instrumentation_tests.py -I --test-apk ContentShellTest -vvv
+desktop$ out/Default/bin/run_$YOUR_TEST
```
