2455a0d8e1
...introduced in 074714fab8db751e2aa0138391a270124733977d ".NET Bindings: Create nuget package for LO SDK". The assumption is that none of the variables used in that block of code represent paths that contain characters that would need any form of quoting. (And if they did, the solution would not be to just wrap them in "..." quoting, but to use '...' and escape any contained ' properly.) Change-Id: Ie5b972c53a60c8c9a4bcfa03627a8e1998646285 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/175010 Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de> Tested-by: Jenkins
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.)
-