sof/lmdk
Adrian Warecki 3bd9991121 lmdk: Instruct linker to keep .buildinfo section
At the beginning of the .text section there must be a structure containing
information about the version of the api used by the library. It's absence
will cause sof to interpret a random literal as a version and incorrectly
load a library.

Signed-off-by: Adrian Warecki <adrian.warecki@intel.com>
2023-11-09 11:28:30 +02:00
..
cmake lmdk: Instruct linker to keep .buildinfo section 2023-11-09 11:28:30 +02:00
include LMDK: Loadable Modules Dev Kit build scripts 2023-05-12 10:56:34 +02:00
libraries/dummy LMDK: Loadable Modules Dev Kit build scripts 2023-05-12 10:56:34 +02:00
modules/dummy LMDK: Loadable Modules Dev Kit build scripts 2023-05-12 10:56:34 +02:00
README.md LMDK: fixed rimage and key paths and discovery 2023-05-16 14:04:32 +03:00

README.md

Loadable Modules Dev Kit

TODO: add link to the documentation repo!

To build dummy loadable library execute:

cd libraries/dummy
cmake -B build -G <Ninja/Makefile> -DRIMAGE_INSTALL_DIR="path/where/rimage/executable/is" -DSNIGNING_KEY="path/to/key"
cd --build build

Here RIMAGE_INSTALL_DIR is a path to directory where rimage executable is, SIGNING_KEY is a path to signing key for rimage. If RIMAGE_INSTALL_DIR is not provided, rimage will be searched for in the directory where SOF project installs it. Dummy module sets up toolchain file in the project file. However, in your library you can select toolchain file in the configure step command:

cmake -B build -G <Ninja/Makefile> --toolchain "../../cmake/xtensa-toolchain.cmake" -DSNIGNING_KEY="path/to/key"