office-gobmx/odk
Hossein 12447b7c70 Fix odk examples build on 32 bit systems
It is required to cast integer literals to sal_Int32 when passing them
to Any().

Change-Id: I377f88fc3441d8e4bc7afdb2411c1fd140853134
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167739
Tested-by: Jenkins
Reviewed-by: René Engelhard <rene@debian.org>
Tested-by: René Engelhard <rene@debian.org>
2024-05-16 17:14:22 +02:00
..
config
docs tdf#160924: SDK: typo SDK_HOME instead of OO_SDK_HOME for linux 2024-05-04 12:16:29 +02:00
examples Fix odk examples build on 32 bit systems 2024-05-16 17:14:22 +02:00
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 use windows doxygen in wsl-as-helper case 2024-05-07 17:08:44 +02:00
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 odk/README.md: easy way to build examples on Linux and macOS 2024-05-10 07:18:25 +02: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.)