1305edfbc2
With LibreOfficeKit (LOK) headers in place, it would be possible to create C++ applications that can access LibreOffice functionality without building LibreOffice, only by installing SDK and build tools. Change-Id: I8efc8ac1cec7b3b89e4d7eb2c8d15afeb595672c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134863 Tested-by: Hossein <hossein@libreoffice.org> Tested-by: Jenkins Reviewed-by: Hossein <hossein@libreoffice.org> |
||
|---|---|---|
| .. | ||
| config | ||
| docs | ||
| examples | ||
| qa/checkapi | ||
| settings | ||
| source | ||
| util | ||
| build-examples_common.mk | ||
| CppunitTest_odk_checkapi.mk | ||
| CustomTarget_allheaders.mk | ||
| CustomTarget_build-examples.mk | ||
| CustomTarget_build-examples_java.mk | ||
| CustomTarget_check.mk | ||
| CustomTarget_classes.mk | ||
| CustomTarget_config_win.mk | ||
| CustomTarget_doxygen.mk | ||
| CustomTarget_html.mk | ||
| CustomTarget_javadoc.mk | ||
| CustomTarget_settings.mk | ||
| Executable_unoapploader.mk | ||
| GeneratedPackage_odk_doxygen.mk | ||
| GeneratedPackage_odk_javadoc.mk | ||
| GeneratedPackage_uno_loader_classes.mk | ||
| index.html | ||
| index_online.html | ||
| Makefile | ||
| Module_odk.mk | ||
| Package_cli.mk | ||
| Package_config.mk | ||
| Package_config_win.mk | ||
| Package_docs.mk | ||
| Package_examples.mk | ||
| Package_html.mk | ||
| Package_odk_headers.mk | ||
| Package_odk_headers_generated.mk | ||
| Package_scripts.mk | ||
| Package_settings.mk | ||
| Package_settings_generated.mk | ||
| Package_share_readme.mk | ||
| Package_share_readme_generated.mk | ||
| README.md | ||
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:
-
The easiest way on Linux and macOS is to run
make odk.subsequentcheck -
The way that also works on Windows is to 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.)
-