summaryrefslogtreecommitdiff
path: root/android
AgeCommit message (Collapse)Author
2012-01-18No need to unpack the .res files any moreTor Lillqvist
2012-01-18android: use config_host.mk for unit test goodnessMichael Meeks
2012-01-16Attempt to manage without Berkeley DB on iOS and AndroidTor Lillqvist
Berkeley DB is used for help index and extension database. (Possibly only for a backward-compatible format of the latter, I am not sure.) Neither use makes much sense on Android and iOS. The existing help is for LO on desktop OSes anyway, help for LO-based apps on iOS and Android will naturally be quite different. On iOS there will definitely be no "extensions", and probably we don't want to bother with such on Android either.
2012-01-15these are not old component files anymoreMatúš Kukan
2012-01-13Now we need libdb, tooTor Lillqvist
2012-01-13Use merged libs on AndroidTor Lillqvist
2012-01-13More workarounds for weird problem with vnd.sun.star.expandTor Lillqvist
2012-01-13Fontconfig must have a cachedir, so hardcode one for nowTor Lillqvist
2012-01-13Just tell to run it with "make run"Tor Lillqvist
2012-01-13We now proceed further and need some more librariesTor Lillqvist
2012-01-12Include .res files, a fonts.conf, and other hackingTor Lillqvist
2012-01-12Add setting environment variablesTor Lillqvist
2012-01-11Need to trim trailing newline from the indirect command line stringTor Lillqvist
2012-01-11Work around http://code.google.com/p/android/issues/detail?id=23351Tor Lillqvist
2012-01-06Merge branch 'feature/gbuild_extensions'Michael Stahl
Conflicts: extensions/source/ole/servreg.cxx extensions/source/plugin/util/makefile.mk postprocess/packcomponents/makefile.mk postprocess/prj/build.lst tail_build/prj/build.lst
2012-01-05Need the basebmp libraryTor Lillqvist
2011-12-24Merge remote-tracking branch 'origin/master' into feature/gbuild_extensionsPeter Foley
Conflicts: Module_tail_build.mk Repository.mk extensions/util/makefile.pmk postprocess/prj/build.lst svx/AllLangResTarget_svx.mk
2011-12-22Add comment about how to use the lo-strace "extra" (option)Tor Lillqvist
2011-12-21Add a couple of missing filesTor Lillqvist
2011-12-19More shlibs and .component files neededTor Lillqvist
2011-12-19This is for Calc unit testsTor Lillqvist
2011-12-18android: delete generated lo-bootstrap.jarMiklos Vajna
2011-12-15Add uninstall targetTor Lillqvist
2011-12-15ndk-gdb needs gdbserver and gdb.setupTor Lillqvist
2011-12-15ucalc needs lots more librariesTor Lillqvist
2011-12-15Add an app for the sc_ucalc unit testTor Lillqvist
2011-12-14Add separate cppunittester app project that uses the Bootstrap libraryTor Lillqvist
2011-12-14Turn Bootstrap into a "library" project from Ant's point of viewTor Lillqvist
2011-12-12Move .gitignore one level upTor Lillqvist
2011-11-30Android code refactorig and hackingTor Lillqvist
Sorry for the large unstructured commit. But hey, the Android code is experimental so far. Extract the native lo-bootstrap code into a fairly normal library built in sal. (Previously it was the JNI part of the "Bootstrap" app.) Just linkink normally to liblo-bootstrap from C++ code that uses it works fine, no need to do a dlsym lookup. Bootstrap is still a subclass of NativeActivity and can thus still be used as an "app" (to start unit tests, or whatever), but can also be used from some other app's Java code to just get access to the lo-bootstrap native methods. Introduce a new top-level "module", android, for Bootstrap and the experiments with DocumentLoader. Note that the experimental DocumentLoader app still crashes. It can't create the com.sun.star.frame.Desktop instance. I spent lots of time debugging in the painfully inadequate ndk-gdb. (Even the newer gdb build from the "mingw-and-ndk" project is quite crappy in many ways.) I should really experiment with corresponding code on a normal platform first before even trying on Android. Basically, I think that if I just can get the concept of Java code that instantiates and uses LO components *in-process* working on a normal desktop platform, it should work on Android, too.
2011-11-29Android hackingTor Lillqvist
Start of an app to just load some document. Uses API from the org.libreoffice.android.Bootstrap class. Not sure what is the sanest way to build an app like this. It needs a bunch of shared libraries of course to be copied into libs/armeabi-v7a so that they get included in the .apk. Perhaps a Makefile similar to the one for lo-bootstrap might be good? But for debugging the Java code Eclipse is the way to go (?), and to be able to do that Eclipse wants a "project". So should this then be built only through Eclipse? Can one build Eclipse projects from the command line?
generated by cgit (git 2.34.1) at 2024-07-13 20:49:19 +0000