Lines Matching +full:built +full:- +full:in

1 .. zephyr:code-sample:: llext-edk
3    :relevant-api: llext_apis
19 run in different contexts. Extensions ``ext1``, ``ext2`` and ``ext3`` run in
22 subscribing to events. Extension ``kext1`` runs in a kernel thread, albeit similar
26 providing some level of isolation - although the kernel one still has access
29 Note that the kernel extension is only available when the EDK is built with
33 The application is built using the Zephyr build system. The EDK is built using
34 the Zephyr build system as well, via ``llext-edk`` target. The EDK is then
35 extracted and the extensions are built using CMake.
40 One could build the extensions in different directories, not related to the
41 Zephyr application - even on different machines, using only the EDK. At the
42 limit, one could even imagine a scenario where the extensions are built by
48 To build the EDK, use the ``llext-edk`` target. For example:
50 .. zephyr-app-commands::
51    :zephyr-app: samples/subsys/llext/edk/app
53    :goals: build llext-edk
54    :west-args: -p=always
59 .. code-block:: console
62     cp build/zephyr/llext-edk.tar.xz /tmp/edk
64     tar -xf llext-edk.tar.xz
68 .. code-block:: console
70     export LLEXT_EDK_INSTALL_DIR=/tmp/edk/llext-edk
80 .. code-block:: console
82     export ZEPHYR_SDK_INSTALL_DIR=</path/to/zephyr-sdk>
84 To build the extensions, in the ``ext1``, ``ext2``, ``ext3`` and ``kext1``
87 .. code-block:: console
89     cmake -B build
90     make -C build
92 Alternatively, you can set the ``LLEXT_EDK_INSTALL_DIR`` directly in the
95 .. code-block:: console
97     cmake -B build -DLLEXT_EDK_INSTALL_DIR=/tmp/edk/llext-edk
98     make -C build
105 .. zephyr-app-commands::
106    :zephyr-app: samples/subsys/llext/edk/app
109    :west-args: -p=always
114 .. code-block:: console
119     [k-ext1]Waiting sem
121     [k-ext1]Waiting event
133     [k-ext1]Got event, giving sem
134     [k-ext1]Got sem, reading channel
135     [k-ext1]Read val: 0
136     [k-ext1]Waiting sem