Lines Matching +full:llext +full:- +full:edk

4 The LLEXT subsystem allows for the creation of extensions that can be loaded
19 application. This can be done using the `LLEXT Extension Development Kit
32 ----------------------
39 .. code-block:: cmake
43        OUTPUT <ext_file.llext>
49 - ``<target_name>`` is the name of the final CMake target that will result in
50   the LLEXT binary being created;
51 - ``<ext_file.llext>`` is the name of the output file that will contain the
53 - ``<src1> [<src2>...]`` is the list of source files that will be compiled to
79 --------------------------
83 functions takes the LLEXT target name as its first argument; it is otherwise
93 ------------------
98 for build-specific details.
102 .. code-block:: cmake
119     After the extension code is built, but before packaging it in an ``.llext``
126     on the final llext file :file:`pkg_output`.
128 Anything else after ``COMMAND`` will be passed to ``add_custom_command()`` as-is
133 LLEXT Extension Development Kit (EDK)
143 (EDK) from the build artifacts of the main Zephyr application, by running the
144 following command which uses the ``llext-edk`` target:
146 .. code-block:: shell
148     west build -t llext-edk
150 The generated EDK can be found in the build directory under the ``zephyr``
155 EDK definition files  argument
156 --------------------
158 The EDK includes several convenience files which define a set of variables that
159 contain the compile flags needed by the project, as well as other build-related
163 - ``Makefile.cflags``, for Makefile-based projects;
164 - ``cmake.cflags``, for CMake-based projects.
166 Paths to the headers and flags are prefixed by the EDK root directory. This is
169 by the user with the path where the EDK is installed before including the
177 -------------
186         Compiler flags to add directories containing non-autogenerated headers
203         build via ``-imacros``.
217 ------------------
219 The EDK includes information that identifies the target of the current Zephyr
241 LLEXT EDK Kconfig options  argument
242 -------------------------
244 The LLEXT EDK can be configured using the following Kconfig options:
247     The name of the generated EDK tarball. This is also used as the prefix for
248     several variables defined in the EDK files.
251     If set, the EDK will include headers that do not contain code to route
255 EDK Sample  argument
256 ----------
258 Refer to :zephyr:code-sample:`llext-edk` for an example of how to use the
259 LLEXT EDK.