Open ceolin opened 4 years ago
AFAIK the only thing the if
is doing there is to express a dependency. So that's the same as writing:
config LOG_BACKEND_RTT_BUFFER
int "Buffer number used for logger output."
range 0 SEGGER_RTT_MAX_NUM_UP_BUFFERS
depends on LOG_BACKEND_RTT_BUFFER
default 0
The Kconfig symbol exists regardless of the value of LOG_BACKEND_RTT_BUFFER
. When the KCONFIG_WARN_UNDEF
option is set I don't see any reason why there should not be a warning because of SEGGER_RTT_MAX_NUM_UP_BUFFERS
not being defined.
In this example from Zephyr, if
SEGGER_RTT_MAX_NUM_UP_BUFFERS
is not defined, kconfiglib is raising a warning even if it is under aif
guard.