1CONFIG_LOG=y
2CONFIG_LOG_MODE_IMMEDIATE=y
3
4# CONFIG_MODULES must be enabled to allow setting any options to "m" in the
5# Kconfig files. For compatibility with Kconfiglib, the name must be kept
6# as-is even if Zephyr has a completely different concept for "modules".
7
8CONFIG_MODULES=y
9
10# LLEXT is only required when loading the extension at runtime. Since in this
11# basic example there's only one llext, leaving it in when building the
12# extension as a built-in is redundant; in a real application, however, there
13# could be other uses of the llext subsystem.
14
15CONFIG_LLEXT=y
16CONFIG_LLEXT_LOG_LEVEL_DBG=y
17CONFIG_LLEXT_HEAP_SIZE=64
18CONFIG_LLEXT_TYPE_ELF_RELOCATABLE=y # supported by all targets
19
20# This test consumes large amounts of stack when loading the LLEXT.
21# Increase the available size to avoid overflowing (see issue #74536).
22
23CONFIG_MAIN_STACK_SIZE=2048
24
25# NOTE
26#
27# This project file explicitly does NOT include the configuration for
28# CONFIG_HELLO_WORLD_MODE, so a clean compile will include the function as
29# built-in by default.
30#
31# To build it as an llext, please follow the instructions in the documentation
32# of this sample; there are architecture-specific settings that must be set in
33# addition to CONFIG_HELLO_WORLD_MODE=m. For example, most ARM targets need to
34# either enable CONFIG_USERSPACE (if they support it) or disable MPU/MMU
35# features for LLEXT to work correctly.
36