Android-specific notes Note that this document has not necessarily been updated to match reality... * Getting something running on an emulated device 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: LD_LIBRARY_PATH=$(pwd)/lib emulator-arm -avd -partition-size 500 In order to have proper acceleration, you need the 32-bit libGL.so: sudo zypper in Mesa-libGL-devel-32bit Where is the literal name of the AVD that you entered. Then: make cmd cmd=bash cd android/qa/sc make clean all install make run ; adb shell logcat And if all goes well - you should have some nice unit test output to enjoy. After a while of this loop you might find that you have lost a lot of space on your emulator's or device's /data volume. If using the emulator, you can do: adb shell stop; adb shell start but on a (non-rooted) device you probably just need to reboot it. On the other hand, this phenomenon might not happen on actual devices. and continue onwards & upwards. * What about using a real device? That works fine, too. You won't be able to use the "adb shell stop" and "adb shell start" commands to do anything, as far as I 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 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. * Common Errors / Gotchas lo_dlneeds: Could not read ELF header of /data/data/org.libreoffice...libfoo.so This (most likely) means that the install quietly failed, and that 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 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 code. Sure, we could quite easily build unit tests as plain Linux executables (built against the Android libraries, of course, not GNU/Linux ones), push them to the device or emulator with adb and run them from adb shell, but that would not be a good test as the environment such processs run in is completely different from that in which real end-user apps with GUI etc run. We have no intent to require LibreOffice code to be used only on "rooted" devices etc. All Android apps are basically Java programs. They run "in" a Dalvik virtual machine. Yes, you can also have apps where all *your* code is native code, written in a compiled language like C or C++. But also also such apps are actually started by system-provided Java bootstrapping code (NativeActivity) running in a Dalvik VM. 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, 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. on value='distro/collabora/dcm-6.2'>distro/collabora/dcm-6.2 LibreOffice 核心代码仓库文档基金会
summaryrefslogtreecommitdiff
path: root/include/LibreOfficeKit
AgeCommit message (Expand)Author
2019-08-15tdf#122529 lok - table border position manipulationTomaž Vajngerl
2019-08-02LOK: Improved selection complexity detectionAshod Nakashian
2019-08-02lok: clipboard: per view clipboard creation.Michael Meeks
2019-08-02Fix build: unused argumentSzymon Kłos
2019-08-02LOK: Support detecting complex selectionsAshod Nakashian
2019-08-02Add more powerful selection fetch & clipboard set methods.Michael Meeks
2019-07-28lok: send cell selection rectangle and cell area fill rectangleTomaž Vajngerl
2019-07-25LOK: support resizing windowsAshod Nakashian
2019-07-25sd: sidebars are now visible in LOOLAshod Nakashian
2019-07-24Fix typoAndrea Gelmini
2019-07-17LOK: support for ordering/moving partsAshod Nakashian
2019-07-10slide-sorter: multiple selectionAshod Nakashian
2019-06-26Fix typosAndrea Gelmini
2019-05-21Fix typoAndrea Gelmini
2019-05-21Fix typoAndrea Gelmini
2019-05-20lok: update graphic selection callback descriptionMarco Cecchetti
2019-05-10an uno -> a unoCaolán McNamara
2019-05-10an is used before a vowel soundCaolán McNamara
2019-05-03libreofficekit: send show/hide messages for dialogsSzymon Kłos
2019-05-02lok: We changed the (unstable) ABI, but let's allow the older C++ API.Jan Holesovsky
2019-04-26lok: allow paste content to popup dialogHenry Castro
2019-04-23LOK: support creating view with optionsAshod Nakashian
2019-04-23Unipoll: add LibreOfficeKit API for polling, and an option to use it.Ashod Nakashian
2019-04-15lok: emit ProfileZone data in messages when requested.Michael Meeks
2019-03-26tdf#124146 support posting of gesture event for LOKitTomaž Vajngerl
2019-03-11android: Separate the Android-specific setup from the actual LOK init.Jan Holesovsky
2019-01-01lok: add signDocument to "Office" iface - to sign not opened docs.Tomaž Vajngerl