|author||Miklos Vajna <email@example.com>||2015-03-19 16:16:55 +0100|
|committer||Miklos Vajna <firstname.lastname@example.org>||2015-03-23 09:19:05 +0100|
android: add debugrun Makefile target
Also, if we are at it: - clean up 'run' as well: since the doc browser is the default activity, no need to pass the test doc path anymore - make 'install' not depend on build: a full build would need a toplevel 'make' anyway Change-Id: Ia55d52f767ab3e0be02a753a95b2aac02f8491cc
Diffstat (limited to 'README.cross')
1 files changed, 3 insertions, 24 deletions
diff --git a/README.cross b/README.cross
index 109588ea5cb0..efaa8c24ed7a 100644
@@ -339,13 +339,8 @@ course need an appropriate system image for that.
Here is an autogen.input for Android on ARM when cross-compiling
And here is an (quite old) autogen.input for Android on X86:
@@ -368,25 +363,9 @@ Note that none of these apps in any way are claimed to be ready for
end-users. No "beta testing" offers needed, it is painfully obvious
what problems they have.
-To run some of the apps, do "make install" followed by either "make
-run" or starting it from Android itself. You most likely want to have
-an "adb logcat" running in another window.
-To debug, do manually what "make run" would do and when the app has
-started, run ndk-gdb.
-You can also do that manually; to install:
- <android-sdk-linux>/platform-tools/adb install -r android/experimental/LOAndroid3/bin/LibreOfficeViewer-debug.apk
-To see the log:
- <android-sdk-linux>/platform-tools/adb logcat
-To debug, install the .apk, run it, and then:
- cd android/experimental/LOAndroid3
- <android-ndk-r9d>/ndk-gdb --adb=<android-sdk-linux>/platform-tools/adb
+To run some of the apps, do "make install" followed by either "make run" or
+starting it from Android itself. You most likely want to have an "adb logcat"
+running in another window. To debug, run "make debugrun".
NB: If you happen to upgrade to Android SDK Tools 23, and the build (using
'make verbose=t android') fails for you with: