Kconfig/style: fix Kconfig style issue
fix this issue reviewed by PR: https://github.com/apache/nuttx/pull/12667 https://github.com/apache/nuttx/pull/12667#discussion_r1699358220 Signed-off-by: chao an <anchao@lixiang.com>
This commit is contained in:
parent
e09a79ece9
commit
cc6accdf16
18
Kconfig
18
Kconfig
|
@ -453,15 +453,15 @@ config OUTPUT_STRIP_PATHS
|
|||
default y
|
||||
depends on ARCH_TOOLCHAIN_GNU
|
||||
---help---
|
||||
Cmake build provide absolute paths to compile files. If __FILE__
|
||||
macros are used in the source code(ASSERT), the binary will contain
|
||||
many invalid paths.
|
||||
This saves some memory, stops exposing build systems locations in binaries,
|
||||
make failure logs more deterministic and most importantly makes builds more
|
||||
failure logs more deterministic and most importantly makes builds more
|
||||
deterministic.
|
||||
Debuggers usually have a path mapping feature to ensure the files are
|
||||
still found.
|
||||
Cmake build provide absolute paths to compile files. If __FILE__
|
||||
macros are used in the source code(ASSERT), the binary will contain
|
||||
many invalid paths.
|
||||
This saves some memory, stops exposing build systems locations in binaries,
|
||||
make failure logs more deterministic and most importantly makes builds more
|
||||
failure logs more deterministic and most importantly makes builds more
|
||||
deterministic.
|
||||
Debuggers usually have a path mapping feature to ensure the files are
|
||||
still found.
|
||||
|
||||
endmenu # Binary Output Formats
|
||||
|
||||
|
|
Loading…
Reference in New Issue