From 75b8f72c3b78ea0762535f1e2c98f4efe3576b59 Mon Sep 17 00:00:00 2001 From: chao an Date: Sun, 4 Aug 2024 19:39:54 +0800 Subject: [PATCH] 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 --- Kconfig | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/Kconfig b/Kconfig index 027fda7b5c25f..2c3fef1530f0d 100644 --- a/Kconfig +++ b/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