Age | Commit message (Collapse) | Author | |
---|---|---|---|
2011-12-24 | Merge remote-tracking branch 'origin/master' into feature/gbuild_extensions | Peter Foley | |
Conflicts: Module_tail_build.mk Repository.mk extensions/util/makefile.pmk postprocess/prj/build.lst svx/AllLangResTarget_svx.mk | |||
2011-12-22 | Add comment about how to use the lo-strace "extra" (option) | Tor Lillqvist | |
2011-12-21 | Add a couple of missing files | Tor Lillqvist | |
2011-12-19 | More shlibs and .component files needed | Tor Lillqvist | |
2011-12-19 | This is for Calc unit tests | Tor Lillqvist | |
2011-12-18 | android: delete generated lo-bootstrap.jar | Miklos Vajna | |
2011-12-15 | Add uninstall target | Tor Lillqvist | |
2011-12-15 | ndk-gdb needs gdbserver and gdb.setup | Tor Lillqvist | |
2011-12-15 | ucalc needs lots more libraries | Tor Lillqvist | |
2011-12-15 | Add an app for the sc_ucalc unit test | Tor Lillqvist | |
2011-12-14 | Add separate cppunittester app project that uses the Bootstrap library | Tor Lillqvist | |
2011-12-14 | Turn Bootstrap into a "library" project from Ant's point of view | Tor Lillqvist | |
2011-12-12 | Move .gitignore one level up | Tor Lillqvist | |
2011-11-30 | Android code refactorig and hacking | Tor 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-29 | Android hacking | Tor 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? |