[Libreoffice-commits] core.git: README.Android
README.Android | 23 +-- 1 file changed, 5 insertions(+), 18 deletions(-) New commits: commit 1256809ba235e1813b38bb7e96d8f1a6c5b6499f Author: Miklos Vajna Date: Mon Dec 8 16:25:49 2014 +0100 README.Android: mention ndk-gdb --start Change-Id: Ib131c480b53665fc9e9a38388e3cc179eac249c2 diff --git a/README.Android b/README.Android index 9ae7fd3..98a109d 100644 --- a/README.Android +++ b/README.Android @@ -46,27 +46,14 @@ know. But don't seem to be necessary on a real device anyway? * Debugging - Install the .apk to the device, start the application, and: + Install the .apk to the device, and: cd android/experimental/LOAndroid3 - /ndk-gdb --adb=/platform-tools/adb + /ndk-gdb --adb=/platform-tools/adb --start - Some versions of the NDK had a broken gdb in the way that it can see -symbols only for shlibs that were already loaded when the debuggee was -attached, so you need to carefully guess where to put: - - fprintf(stderr, "Sleeping NOW!\n"); ::sleep(20); - - into the code; and when you see that in logcat, you have time -to run: ndk-gdb and it will attach the process. - - thread 12 # or perhaps 13 - backtrace - - may show you the native code trace. - - In r8b the ndk-gdb seems to work a bit better, and I think it isn't -necessary to use the mingw-and-ndk ndb-gdb any longer. + It seems that the "have to start the app before gdb can connect to it" +and the "pending breakpoints do not work" problems are now resolved with the +current NDK. * Getting the symbols ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android README.cross
README.Android |5 + README.cross | 13 + 2 files changed, 18 insertions(+) New commits: commit c862be08158f502c42752f025d5cc6384285c688 Author: Jan Holesovsky Date: Mon Oct 13 16:51:08 2014 +0200 android: Dump my debugging notes to the readme's. Change-Id: I8f91e73fe5df5dfef054df80d43be3c74d01388b diff --git a/README.Android b/README.Android index 2fe09e2..9ae7fd3 100644 --- a/README.Android +++ b/README.Android @@ -46,6 +46,11 @@ know. But don't seem to be necessary on a real device anyway? * Debugging + Install the .apk to the device, start the application, and: + + cd android/experimental/LOAndroid3 + /ndk-gdb --adb=/platform-tools/adb + Some versions of the NDK had a broken gdb in the way that it can see symbols only for shlibs that were already loaded when the debuggee was attached, so you need to carefully guess where to put: diff --git a/README.cross b/README.cross index 451751d..0c6a777 100644 --- a/README.cross +++ b/README.cross @@ -375,6 +375,19 @@ 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: + + /platform-tools/adb install -r android/experimental/LOAndroid3/bin/LibreOfficeViewer-debug.apk + +To see the log: + + /platform-tools/adb logcat + +To debug, install the .apk, run it, and then: + + cd android/experimental/LOAndroid3 + /ndk-gdb --adb=/platform-tools/adb + NB: If you happen to upgrade to Android SDK Tools 23, and the build (using 'make verbose=t android') fails for you with: ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android
README.Android |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 04a65e2704ee80701ca750f2e7c8c0565d2aa830 Author: xjcl Date: Mon Aug 4 21:33:49 2014 +0200 typo: and -> an diff --git a/README.Android b/README.Android index 9d022a7..2fe09e2 100644 --- a/README.Android +++ b/README.Android @@ -9,7 +9,7 @@ For instructions on how to build for Android, see README.cross. Create an AVD in the android UI, don't even try to get the data partition size right in the GUI, that is doomed to producing -and AVD that doesn't work. Instead start it from the console: +an AVD that doesn't work. Instead start it from the console: LD_LIBRARY_PATH=$(pwd)/lib emulator-arm -avd -partition-size 500 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android
README.Android | 15 +++ 1 file changed, 15 insertions(+) New commits: commit d641b54efcbea5af1074acc2335fb00c6c845c1e Author: Jan Holesovsky Date: Mon Jul 14 16:54:11 2014 +0200 android: Hint how to get the symbols, but not a 1.5G .apk. Change-Id: I6f6d2e7516d99a02ad813ba5e03c5cdcac2f4964 diff --git a/README.Android b/README.Android index 68bec24..9d022a7 100644 --- a/README.Android +++ b/README.Android @@ -63,6 +63,21 @@ to run: ndk-gdb and it will attach the process. In r8b the ndk-gdb seems to work a bit better, and I think it isn't necessary to use the mingw-and-ndk ndb-gdb any longer. +* Getting the symbols + +In order to be able to debug, you also need the symbols. Currently they are +stripped using a $(STRIP) call in android/Bootstrap/Makefile.shared ; make +sure you change it only to 'cp'. + +But then you need to limit the size of the resulting binary by other means, +that is strip most of the symbols (but the interesting ones) already during +the build. For that, use something like + +--enable-dbgutil +--enable-selective-debuginfo="sal/" + +in your autogen.input (but of course limit the --enable-selective-debuginfo +only to directories / libraries that are interesting to you). * Common Errors / Gotchas ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android README.cross
README.Android |4 +++- README.cross |8 +++- 2 files changed, 6 insertions(+), 6 deletions(-) New commits: commit 2462aa668f7109fc40de9fbf5e13e1f3fdf904cd Author: Tor Lillqvist Date: Fri Feb 21 22:37:47 2014 +0200 Minor updates Change-Id: I8f3580f10e8beee4103780be71a08929e9000bf0 diff --git a/README.Android b/README.Android index 3a78e76..68bec24 100644 --- a/README.Android +++ b/README.Android @@ -1,7 +1,9 @@ Android-specific notes Note that this document has not necessarily been updated to match -reality... +reality... + +For instructions on how to build for Android, see README.cross. * Getting something running on an emulated device diff --git a/README.cross b/README.cross index 49fe05e..74917fa 100644 --- a/README.cross +++ b/README.cross @@ -345,12 +345,12 @@ from Linux: --enable-dbgutil --enable-debug --enable-werror ---with-android-ndk=/home/tml/android-ndk-r8d ---with-android-ndk-toolchain-version=4.6 +--with-android-ndk=/home/tml/android-ndk-r9c +--with-android-ndk-toolchain-version=4.8 --with-android-sdk=/home/tml/adt-bundle-linux/sdk --with-distro=LibreOfficeAndroid -And here is an autogen.input for Android on X86: +And here is an (quite old) autogen.input for Android on X86: --with-android-ndk=/opt/libreoffice/android-ndk-r8b --with-android-ndk-toolchain-version=4.6 @@ -358,8 +358,6 @@ And here is an autogen.input for Android on X86: --build=i586-suse-linux --enable-ccache --with-distro=LibreOfficeAndroidX86 ---with-num-cpus=6 ---with-max-jobs=6 There are a couple of (more or less) interactive apps that you can run on the emulator or on a device that use LibreOffice code. Look in ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android
README.Android | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) New commits: commit 1371d07009b29539fe84595bf1a0c81afeb3eee5 Author: Tor Lillqvist Date: Wed Dec 18 12:41:34 2013 +0200 Drop some obsolete stuff Change-Id: Icc6bf58c295591347a3079d2a5312e1904e57060 diff --git a/README.Android b/README.Android index 2bf1f44..3a78e76 100644 --- a/README.Android +++ b/README.Android @@ -44,12 +44,7 @@ know. But don't seem to be necessary on a real device anyway? * Debugging - Debugging is fun, the default NDK gdb (in v7) is busted, you -need to download a new one from: - - http://code.google.com/p/mingw-and-ndk/ - - Even this 'fixed' gdb is broken in the way that it can see + Some versions of the NDK had a broken gdb in the way that it can see symbols only for shlibs that were already loaded when the debuggee was attached, so you need to carefully guess where to put: @@ -76,6 +71,9 @@ the file is truncated; check it out with adb shell ls -l /data/data/ * Detailed explanation +Note: the below talk about unit tests is obsolete; we no longer have +any makefilery etc to build unit tests for Android. + Unit tests are the first thing we want to run on Android, to get some idea how well, if at all, the basic LO libraries work. We want to build even unit tests as normal Android apps, i.e. packaged as .apk ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android
README.Android |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 971228af97b3b5372d760e1280971a90ca7f9c7b Author: Miklos Vajna Date: Sat Nov 23 16:06:47 2013 +0100 README.Android: typo Change-Id: I439f2ca86614c30b75e22959f982278591185d40 diff --git a/README.Android b/README.Android index 4b8c8d2..2bf1f44 100644 --- a/README.Android +++ b/README.Android @@ -77,7 +77,7 @@ the file is truncated; check it out with adb shell ls -l /data/data/ * Detailed explanation Unit tests are the first thing we want to run on Android, to get some -idea how well, if at all, the basic LO libraraies work. We want to +idea how well, if at all, the basic LO libraries work. We want to build even unit tests as normal Android apps, i.e. packaged as .apk files, so that they run in a sandboxed environment like that of whatever eventual end-user Android apps there will be that use LO ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android
README.Android |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 9b1e83c4f5922029ca7cd61b73bd0f8695aadedb Author: Viktor Varga Date: Wed Aug 28 11:19:52 2013 +0200 typo fix Change-Id: Ie57db4581bb10e5f7fbd5e7a6668574ab6dbc271 Reviewed-on: https://gerrit.libreoffice.org/5657 Reviewed-by: Andras Timar Tested-by: Andras Timar diff --git a/README.Android b/README.Android index ac11fb9..4b8c8d2 100644 --- a/README.Android +++ b/README.Android @@ -102,7 +102,7 @@ executable program, but as a shared object. The Java NativeActivity bootstrapper loads that shared object with dlopen. Anyway, our current "experimental" apps (DocumentLoader, -LibreOffice4Android and LibreOfficeDesbktop) are not based on +LibreOffice4Android and LibreOfficeDesktop) are not based on NativeActivity any more. They have normal Java code for the activity, and just call out to a single, app-specific native library (called liblo-native-code.so) to do all the heavy lifting. ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: README.Android README.cross
README.Android | 33 +- README.cross | 274 - 2 files changed, 143 insertions(+), 164 deletions(-) New commits: commit 30fded6a91c8803f656a50755b9e83a1e07edc08 Author: Tor Lillqvist Date: Mon Mar 18 09:24:41 2013 +0200 Some edits to improve match with current reality Change-Id: Ieb2839a3416b1ff7d8f8b5f557f98116115eb1ce diff --git a/README.Android b/README.Android index f86c872..ac11fb9 100644 --- a/README.Android +++ b/README.Android @@ -101,31 +101,8 @@ Such a native app (or actually, "activity") is not built as a executable program, but as a shared object. The Java NativeActivity bootstrapper loads that shared object with dlopen. -Anyway, our current "experimental" apps (DocumentLoader and -LibreOffice4Android) are not based on NativeActivity any more. They -have normal Java code for the activity, and just call out to native -libraries to do all the heavy lifting. - -It is somewhat problematic to construct .apk packages except by using -the high-level tools in the Android SDK. At least I haven't figured -out how to manually construct an .apk that is properly signed so that -it will run in the emulator. (I don't have any Android device...) I -only know how to let the SDK Ant tooling do it... - -At this stage, the plan is that a LO Android app will work would -something like this: - -We have a Java class org.libreoffice.android.Bootstrap that that loads -a small helper native library liblo-bootstrap.so that implements JNI -wrappers for dlopen(), dlsym(), and ELF header scanning coresponding -to looking for DT_NEEDED entries with readelf. - -The Java code then loads the actual native library that corresponds to -the LibreOffice-related "program" we want to run. For unit tests, a -library that corresponds to cppunittester program. Then through helper -functions in liblo-bootstrap it calls a named function in that -"program". - -This Android-specific native code (the lo-bootstrap library) is for -now in sal/android, and the Java code in the android "module" -(subdirectory right here). +Anyway, our current "experimental" apps (DocumentLoader, +LibreOffice4Android and LibreOfficeDesbktop) are not based on +NativeActivity any more. They have normal Java code for the activity, +and just call out to a single, app-specific native library (called +liblo-native-code.so) to do all the heavy lifting. diff --git a/README.cross b/README.cross index b5624b7..bbb9df6 100644 --- a/README.cross +++ b/README.cross @@ -1,8 +1,8 @@ Cross-compiling LibreOffice -=== +*** -Cross-compilation work has been done, to various degrees, for platforms: -Windows, iOS, Android, PowerPC Mac OS X, Raspbian. +Cross-compilation works, to various degree, to the following +platforms: Windows, iOS, Android, PowerPC Mac OS X, Raspbian. General @@ -26,47 +26,53 @@ Even though the LibreOffice build mechanism is highly unorthodox, the configure script takes the normal --build and --host options like any GNU Autoconf -based configure script. To cross-compile, you basically need just to specify a suitable --host option and things should work -out nicely. In practise, many details needed to be handled. See -examples below. +out nicely. In practice, many details need to be handled. See examples +below. + +Note that in the case of LibreOffice, it is uncommon to run the +configure script directly. Normally one uses the autogen.sh script. +The autogen.sh script saves its last command-line options used in a +file called autogen.lastrun. The typical way of working is to edit +this file, i.e. use it as an input file to autogen.sh and not as a +saved backup copy of command-line parameters. What is so hard, then? -- Despite the fact that the configure script takes normal --build and ---host options, that is just the beginning. In practise a lot of work -was necessary to separate tests for "host" and "build" platforms in -the configure script. See the git log for details. And the reasonably -"standard" configure.in is just the top level; when we get down to the -actual makefilery used to build the bits of LibreOffice, it gets much -worse. +--host options, that is just the beginning. It was necessary to +separate tests for "host" and "build" platforms in the configure +script. See the git log for details. And the reasonably "standard" +configure.in is just the top level; when we get down to the actual +makefilery used to build the bits of LibreOffice, it gets much worse. Windows - -There is some support in LibreOffice already (from OpenOffice.org) for -building it locally on Windows with the GNU tool-chain -(MinGW). Apparently, that work has never attempted cross-compilation. - -This OOo-originated MinGW support attempts to support both running -Cygwin gcc in its -mno-cygwin mode, and a native MinGW compiler. The --mno-cygwin mechanism in the Cygwin gcc is rapidly being obsol
