zephyr/subsys/logging/Kconfig.template.log_format_config
Krzysztof Chruściński 8652e8e413 logging: Fix LOG_OUTPUT dependency
When CONFIG_LOG_OUTPUT is set, it indicates that logging strings
are formatted by the application (using log_output module). It is
not needed when backend works in the dictionary mode. So far
LOG_OUTPUT was set also when dictionary mode was used and that
prevented removing of the logging strings from binary which is
an important feature of the dictionary logging.

Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2024-10-09 18:37:49 +01:00

45 lines
1.4 KiB
Text

# Copyright (c) 2022 Intel Corporation.
# SPDX-License-Identifier: Apache-2.0
choice "LOG_BACKEND_$(backend)_OUTPUT"
prompt "Backend Output Mode"
default LOG_BACKEND_$(backend)_OUTPUT_TEXT
config LOG_BACKEND_$(backend)_OUTPUT_TEXT
bool "Text"
select LOG_OUTPUT
help
Output in text.
config LOG_BACKEND_$(backend)_OUTPUT_SYST
bool "MIPI SyS-T"
depends on LOG_MIPI_SYST_ENABLE
help
When enabled backend is used to output syst format logs.
config LOG_BACKEND_$(backend)_OUTPUT_DICTIONARY
bool "Dictionary"
select LOG_DICTIONARY_SUPPORT
imply LOG_FMT_SECTION
imply LOG_FMT_SECTION_STRIP if !LOG_ALWAYS_RUNTIME
help
Backend is in dictionary-based logging output mode.
config LOG_BACKEND_$(backend)_OUTPUT_CUSTOM
bool "Extern"
help
Custom formatting function can be set externally.
endchoice
# The numbering of the format types should be consistent across
# all the backends in the Kconfig and their values must match
# LOG_OUTPUT_XXX type in C files.
# Example : LOG_BACKEND_XXX_OUTPUT_TEXT should be numbered 0 across all backends
# and should match the value of LOG_OUTPUT_TEXT defined in log_output.h
config LOG_BACKEND_$(backend)_OUTPUT_DEFAULT
int
default 0 if LOG_BACKEND_$(backend)_OUTPUT_TEXT
default 1 if LOG_BACKEND_$(backend)_OUTPUT_SYST
default 2 if LOG_BACKEND_$(backend)_OUTPUT_DICTIONARY
default 3 if LOG_BACKEND_$(backend)_OUTPUT_CUSTOM