# How to make message logs prettier, more coherent
**URL:** https://discourse.cmake.org/t/how-to-make-message-logs-prettier-more-coherent/15596
**Category:** Code
**Created:** [April 7, 2026, 1:34pm UTC](https://discourse.cmake.org/t/how-to-make-message-logs-prettier-more-coherent/15596 "2026-04-07T13:34:21Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Maaz\_Madha](https://discourse.cmake.org/u/Maaz_Madha)
#### Post date: [April 7, 2026, 1:34pm UTC](https://discourse.cmake.org/t/how-to-make-message-logs-prettier-more-coherent/15596/1 "2026-04-07T13:34:21Z")
Hi all
I have outputs from my build that look like this
> build] C:/msc\_file\_explorer/msc\_file\_explorer/tusb\_config/tusb\_config.h:54:9: warning: “CFG\_TUSB\_DEBUG” redefined
>
> [build] 54 | #define CFG\_TUSB\_DEBUG 2
>
> [build] | ^ ~~~~~~~~~~~~~
>
> [build] : note: this is the location of the previous definition
>
> [build] [12/408] Building C object fatfs/CMakeFiles/fatfs\_lib.dir/C\_/pico-sdk/lib/tinyusb/src/class/cdc/cdc\_host.c.obj
>
> [build] In file included from C:/pico-sdk/lib/tinyusb/src/tusb\_option.h:243,
>
> [build] from C:/pico-sdk/lib/tinyusb/src/class/cdc/cdc\_host.c:30:
>
> [build] C:/msc\_file\_explorer/msc\_file\_explorer/tusb\_config/tusb\_config.h:54:9: warning: “CFG\_TUSB\_DEBUG” redefined
>
> [build] 54 | #define CFG\_TUSB\_DEBUG 2
>
> [build] | ^ ~~~~~~~~~~~~~
>
> [build] : note: this is the location of the previous definition
>
> [build] [13/408] Building C object fatfs/CMakeFiles/fatfs\_lib.dir/C\_/pico-sdk/lib/tinyusb/src/class/vendor/vendor\_host.c.obj
>
> [build] In file included from C:/pico-sdk/lib/tinyusb/src/tusb\_option.h:243,
>
> [build] from C:/pico-sdk/lib/tinyusb/src/class/vendor/vendor\_host.c:27:
>
> [build] C:/msc\_file\_explorer/msc\_file\_explorer/tusb\_config/tusb\_config.h:54:9: warning: “CFG\_TUSB\_DEBUG” redefined
>
> [build] 54 | #define CFG\_TUSB\_DEBUG 2
>
> [build] | ^ ~~~~~~~~~~~~~
>
> [build] : note: this is the location of the previous definition
>
> [build] [14/408] Building C object fatfs/CMakeFiles/fatfs\_lib.dir/C\_/pico-sdk/lib/tinyusb/src/portable/raspberrypi/pio\_usb/hcd\_pio\_usb.c.obj
>
> [build] FAILED: [code=1] fatfs/CMakeFiles/fatfs\_lib.dir/C\_/pico-sdk/lib/tinyusb/src/portable/raspberrypi/pio\_usb/hcd\_pio\_usb.c.obj
>
> [build] C:\Users\Mypc\.pico-sdk\toolchain\14\_2\_Rel1\bin\arm-none-eabi-gcc.exe -DCFG\_TUSB\_DEBUG=1 -DCFG\_TUSB\_MCU=OPT\_MCU\_RP2040 -DCFG\_TUSB\_OS=OPT\_OS\_PICO -DLIB\_BOOT\_STAGE2\_HEADERS=1 -DLIB\_PICO\_ATOMIC=1 -DLIB\_PICO\_BIT\_OPS=1 -DLIB\_PICO\_BIT\_OPS\_PICO=1 -DLIB\_PICO\_CLIB\_INTERFACE=1 -DLIB\_PICO\_CRT0=1 -DLIB\_PICO\_CXX\_OPTIONS=1 -DLIB\_PICO\_DIVIDER=1 -DLIB\_PICO\_DIVIDER\_HARDWARE=1 -DLIB\_PICO\_DOUBLE=1 -DLIB\_PICO\_DOUBLE\_PICO=1 -DLIB\_PICO\_FLASH=1 -DLIB\_PICO\_FLOAT=1 -DLIB\_PICO\_FLOAT\_PICO=1 -DLIB\_PICO\_INT64\_OPS=1 -DLIB\_PICO\_INT64\_OPS\_PICO=1 -DLIB\_PICO\_MALLOC=1 -DLIB\_PICO\_MEM\_OPS=1 -DLIB\_PICO\_MEM\_OPS\_PICO=1 -DLIB\_PICO\_NEWLIB\_INTERFACE=1 -DLIB\_PICO\_PLATFORM=1 -DLIB\_PICO\_PLATFORM\_COMMON=1 -DLIB\_PICO\_PLATFORM\_COMPILER=1 -DLIB\_PICO\_PLATFORM\_PANIC=1 -DLIB\_PICO\_PLATFORM\_SECTIONS=1 -DLIB\_PICO\_PRINTF=1 -DLIB\_PICO\_PRINTF\_PICO=1 -DLIB\_PICO\_RUNTIME=1 -DLIB\_PICO\_RUNTIME\_INIT=1 -DLIB\_PICO\_STANDARD\_BINARY\_INFO=1 -DLIB\_PICO\_STANDARD\_LINK=1 -DLIB\_PICO\_STDIO=1 -DLIB\_PICO\_STDIO\_UART=1 -DLIB\_PICO\_STDLIB=1 -DLIB\_PICO\_SYNC=1 -DLIB\_PICO\_SYNC\_CRITICAL\_SECTION=1 -DLIB\_PICO\_SYNC\_MUTEX=1 -DLIB\_PICO\_SYNC\_SEM=1 -DLIB\_PICO\_TIME=1 -DLIB\_PICO\_TIME\_ADAPTER=1 -DLIB\_PICO\_UNIQUE\_ID=1 -DLIB\_PICO\_UTIL=1 -DLIB\_TINYUSB\_BOARD=1 -DLIB\_TINYUSB\_HOST=1 -DPICO\_32BIT=1 -DPICO\_BOARD=\“pico\” -DPICO\_BUILD=1 -DPICO\_CMAKE\_BUILD\_TYPE=\“Debug\” -DPICO\_COPY\_TO\_RAM=0 -DPICO\_CXX\_ENABLE\_EXCEPTIONS=0 -DPICO\_NO\_FLASH=0 -DPICO\_NO\_HARDWARE=0 -DPICO\_ON\_DEVICE=1 -DPICO\_RP2040=1 -DPICO\_USE\_BLOCKED\_RAM=0 -DRP2040\_USB\_HOST\_MODE=1 -IC:/msc\_file\_explorer/msc\_file\_explorer/tusb\_config -IC:/msc\_file\_explorer/msc\_file\_explorer/fatfs -IC:/pico-sdk/lib/tinyusb/src -IC:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_atomic/include -IC:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/tinyusb/include -IC:/pico-sdk/lib/tinyusb/hw -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2040/hardware\_structs/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2040/hardware\_regs/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_base/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/common/pico\_base\_headers/include -isystem C:/msc\_file\_explorer/msc\_file\_explorer/build/pico-debug/generated/pico\_base -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/boards/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2040/pico\_platform/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_platform\_common/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_platform\_compiler/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_platform\_panic/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_platform\_sections/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_irq/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/common/hardware\_claim/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_sync/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_sync\_spin\_lock/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/common/pico\_sync/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/common/pico\_time/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_timer/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/common/pico\_util/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_time\_adapter/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_runtime\_init/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_clocks/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_gpio/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_resets/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_pll/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_vreg/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_watchdog/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/hardware\_ticks/include -isystem C:/Users/Mypc/.pico-sdk/sdk/2.2.0/src/rp2\_common/pico\_bootrom/include -isystem C:
My Q is that is there anyway to make this prettier, or more coherent(organised) so that its not an eyesore to look at.
Kind regards
---
### Author:  [@retif](https://discourse.cmake.org/u/retif)
#### Post date: [April 7, 2026, 2:19pm UTC](https://discourse.cmake.org/t/how-to-make-message-logs-prettier-more-coherent/15596/2 "2026-04-07T14:19:02Z")
As far as I can tell, this isn’t a CMake output but a compiler’s, so you’d need to address that Q to your compiler (_GCC?_) maintainers.