Lines Matching refs:extension

9 The easiest path to achieve this is to build the extension as part of the
12 main Zephyr application and the extension(s), which will all automatically be
16 convenient; maybe the extension is built using a different compiler suite or as
17 part of a different project altogether. In this case, the extension developer
31 Building the extension
34 An extension can be defined in the app's ``CMakeLists.txt`` by invoking the
52   packaged extension;
54   create the extension.
56 The exact steps of the extension building process depend on the currently
76     The final extension file name.
82 during the extension build process to a fine degree. Each of the below
96 that will be executed during the extension build process. The command will be
114     Before the extension code is linked, if the architecture uses dynamic
119     After the extension code is built, but before packaging it in an ``.llext``
125     After the extension output file has been created. The command can operate
139 a direct impact on how Zephyr headers are interpreted and the extension is
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
193         All flags required to build an extension. This is a combination of