chromium/src
0
Fork 0
Code Activity

WebView: update outdated docs for test shell

Browse Source 
WebView no longer supports the android_webview_apk target for anything
other than automated testing. Keeping docs for building an unsupported
target is misleading, especially since android_webview_apk is not
actually a WebView.

This CL keeps the description about WebView, but removes the parts
about the test shell. It has a pointer to our team's chromium wiki page
for building and installing AOSP WebView.

This renames the section to "Build WebView" instead of "Build WebView
shell" to reflect the update.

BUG=703376

Review-Url: https://codereview.chromium.org/2770983007
Cr-Commit-Position: refs/heads/master@{#459221}
This commit is contained in:
ntfschr
2017-03-23 14:17:08 -07:00
committed by Commit bot
parent 9a467e1877
commit 29a7adabb3
1 changed files with 5 additions and 19 deletions

24
docs/android_build_instructions.md

@ -224,23 +224,16 @@ CHROMIUM_OUT_DIR env.
export CHROMIUM_OUT_DIR=out_android
```
### Build WebView shell
### Build WebView
[Android WebView](https://developer.android.com/reference/android/webkit/WebView.html)
is a system framework component. Since Android KitKat, it is implemented using
Chromium code (based off the [content module](https://dev.chromium.org/developers/content-module)).
It is possible to test modifications to WebView using a simple test shell. The
WebView shell is a view with a URL bar at the top (see [code](https://code.google.com/p/chromium/codesearch#chromium/src/android_webview/test/shell/src/org/chromium/android_webview/test/AwTestContainerView.java))
and is **independent** of the WebView **implementation in the Android system** (
the WebView shell is essentially a standalone unbundled app).
As drawback, the shell runs in non-production rendering mode only.
```shell
ninja -C out/Release android_webview_apk
build/android/adb_install_apk.py out/Release/apks/AndroidWebView.apk
```
If, instead, you want to build the complete Android WebView framework component and test the effect of your chromium changes in other Android app using the WebView, you should follow the [Android AOSP + chromium WebView instructions](https://www.chromium.org/developers/how-tos/build-instructions-android-webview)
If you want to build the complete Android WebView framework component and test
the effect of your chromium changes in Android apps using WebView, you should
follow the [Android AOSP + chromium WebView
instructions](https://www.chromium.org/developers/how-tos/build-instructions-android-webview)
### Running
@ -258,12 +251,6 @@ For Chrome public:
build/android/adb_run_chrome_public http://example.com
```
For Android WebView shell:
```shell
build/android/adb_run_android_webview_shell http://example.com
```
### Logging and debugging
Logging is often the easiest way to understand code flow. In C++ you can print
@ -284,7 +271,6 @@ following commands:
```shell
build/android/adb_gdb_content_shell
build/android/adb_gdb_chrome_public
build/android/adb_gdb_android_webview_shell http://example.com
```
See [Debugging Chromium on Android](https://www.chromium.org/developers/how-tos/debugging-on-android)