Lines Matching full:extensions

2    :name: Linkable loadable extensions EDK
13 extensions that it loads. The provided API is a simple publish/subscribe system,
14 based on :ref:`Zbus <zbus>`, which extensions use to communicate with each other.
17 published and republishes them via Zbus to the extensions that are
18 subscribers. There are four extensions, which are loaded by the application and
19 run in different contexts. Extensions ``ext1``, ``ext2`` and ``ext3`` run in
35 extracted and the extensions are built using CMake.
37 Finally, the way the application loads the extensions is by including them
39 providing the ability to build extensions independently from the application.
40 One could build the extensions in different directories, not related to the
42 limit, one could even imagine a scenario where the extensions are built by
72 This variable is used by the extensions to find the EDK.
74 Building the extensions
78 extensions to find the Zephyr SDK, so you need to ensure it's properly set:
84 To build the extensions, in the ``ext1``, ``ext2``, ``ext3`` and ``kext1``
103 Now, build the application, including the extensions, and run it: