Files
odfstudio/odk
Daniel Lee 48f289231c tdf#155956 Fix Windows sdk setup script
Changed script so it detects OS bitness and finds vcvars32.bat
or vcvars64.bat by searching through the VS installation
that contains the C++ compiler

Change-Id: I9fc5708e5c80e10976d9d55b662178e360aeed62
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/196260
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <stephan.bergmann@collabora.com>
2026-03-11 15:30:54 +01:00
..
2026-01-02 19:28:56 +01:00
2025-03-30 14:38:05 +02:00
…
2026-01-02 19:28:56 +01:00
2026-01-02 19:28:56 +01:00
…
…

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 in odk/)

  • 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 each make invocation) each of the SDK's examples/ 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.)