Lines Matching full:build

9 The easiest path to achieve this is to build the extension as part of the
11 <llext_build_native_>`_. This will result in a single build providing both the
15 In some cases, involving the full Zephyr build system may not be feasible or
27 The Zephyr build system provides a set of features that can be used to build
28 extensions as part of the Zephyr application. This is the simplest way to build
29 extensions, as it requires minimal additions to an application build system.
78 Tweaking the build process
81 The following CMake functions can be used to modify the build system behavior
82 during the extension build process to a fine degree. Each of the below
92 Custom build steps
95 The ``add_llext_command`` CMake function can be used to add custom build steps
96 that will be executed during the extension build process. The command will be
97 run at the specified build step and can refer to the properties of the target
98 for build-specific details.
110 The different build steps are:
137 build system, it's important to have access to the same set of generated
143 (EDK) from the build artifacts of the main Zephyr application, by running the
148     west build -t llext-edk
150 The generated EDK can be found in the build directory under the ``zephyr``
152 to build extensions. The extension developer can then include the headers
153 and use the compile flags in their build system to build the extension.
161 of flags needed to build an extension is provided by ``LLEXT_CFLAGS``. Also
178         build to the compiler's include search paths. This is a combination of
184         build via ``-imacros``.
193         All flags required to build an extension. This is a combination of