This commit merges the code of the document browser found in
android/experimental/LibreOffice4Android into the new document viewer
at LOAndroid3. All the source and resources is moved, and some
duplicated files are removed.
From now on the apk generated by LOAndroid3 will provide the document
browser too.
Slightly modified the build files of ExperimentalDesktop project
because they depended on LibreOffice4Android being built.
Change-Id: I0579afda7b570509ca4d3873c28a13fcbeeb5ab8
Reviewed-on: https://gerrit.libreoffice.org/11487
Reviewed-by: Tomaž Vajngerl <quikee@gmail.com>
Tested-by: Tomaž Vajngerl <quikee@gmail.com>
LOAndroid3 is based of LibreOffice4Android project which uses
ant/make for building. By using LibreOffice4Android as the base,
the project creates a APK archive which has all needed files
to start LibreOffice in Android environment.
Change-Id: I697d5f727bdaf93e774144ad597d7081d2609908
Previously the Impress Remote app could only be built within
gbuild when building the entirety of LO for Android, it can
now be enabled separately to be built within any LO build.
(Note that the app could still be built separately without doing a
full Android build of LO by using the android build tools and/or IDE.)
Conflicts:
config_host.mk.in
Change-Id: I21d4389082a1492a3c9029d630f3fff97d9ba99a
Reviewed-on: https://gerrit.libreoffice.org/6146
Reviewed-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
Tested-by: Björn Michaelsen <bjoern.michaelsen@canonical.com>
Serialize the Ant cleaning and building of android/abs-lib so that one
Ant is not cleaning it while another is building something that
depends on it.
Change-Id: I22fde47bf84208fa129b8f6a65a2314c885451a0
Just build the sdremote app for now. Note that this is a pure Java
app with no dependencies on (native) code (or Java code, for that
matter) from rest of LO.
Probably should drop the separate android/sdremote/Makfile and just do
what it does in android/CustomTarget_sdremote.mk instead.
Adding other Android apps (well, the LibreOffice4Android one likely)
to gbuild will require more complexity as they bundle native code, and
thus should depend on other modules first having been built. If one
wants to go really fancy, one could of course depend on the specific
libraries (and other files) being bundled. Let's see...
Change-Id: If10761479f348c4993eec40b7f8346edb77f0e0d
