Stephan Bergmann
b21cab3f17
At least on Linux, with a --with-lang=ALL build, `LANGUAGE=de make CustomTarget_odk/build-examples_java' would fail, as it would ask for license agreement in German rather than English (presumably because the code in getUILangFromEnvironment, i18nlangtag/source/isolang/inunx.cxx, inspects the LANGUAGE env var fist thing), so would expect a "ja" rather than the "yes" we feed into stdin. Change-Id: If285e4458e0706102a62f4e0094e5144575ccf7b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/158998 Reviewed-by: Samuel Mehrbrodt <samuel.mehrbrodt@allotropia.de> Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Office Development Kit (odk)
Office development kit (odk) - implements the first step on the way to the LibreOffice SDK
tarball.
Part of the SDK; to build you need to add --enable-odk.
Testing the Examples:
-
Go to
instdir/sdk(Don't try directly inodk/) -
See https://api.libreoffice.org/docs/install.html how to set up the SDK.
- When asked about it during configuration, tell the SDK to do automatic deployment of the example extensions that get built.
-
In a shell set up for SDK development, build (calling
make) and test (following the instructions given at the end of eachmakeinvocation) each of the SDK'sexamples/sub-directories.-
An example script to build (though not test) the various examples in batch mode is
find examples \( -type d -name nativelib -prune \) -o \\( -name Makefile -a -print -a \( -execdir make \; -o -quit \) \)(Note that one of the example extensions asks you to accept an example license on stdin during deployment.)
-