core/lib: control assert with CONFIG_* macros

[maribu]

Contribution description

This brings the compile time configuration of assert in line with current expectations:

1. Use a CONFIG_ prefix
2. The value needs to be defined as 1 to enable a feature. When undefined or defined as 0, the feature is disabled.

To not break existing code, backward compatibility is added. If the old macros are used, a notice about the use of the deprecated macro and what to use instead is printed.

Testing procedure

Adding CFLAGS += -DDEBUG_ASSERT_VERBOSE should still give verbose assertion messages, but also print:

core/lib/assert.c:31:11: note: '#pragma message: Macro -DDEBUG_ASSERT_VERBOSE is deprecated, use -DCONFIG_ASSERT_VERBOSE=1 instead'
   31 | #  pragma message "Macro -DDEBUG_ASSERT_VERBOSE is deprecated, use -DCONFIG_ASSERT_VERBOSE=1 instead"
      |           ^~~~~~~

Adding CFLAGS += -DCONFIG_ASSERT_VERBOSE=1 should give verbose asserts, e.g.

2025-12-19 17:09:55,674 # main(): This is RIOT! (Version: 2026.01-devel-290-g56b29-assert/use-config-prefix)
2025-12-19 17:09:55,675 # examples/basic/hello-world/main.c:25 => FAILED ASSERTION.

Defining it to 0 or not defining it should give compact asserts instead, e.g.

2025-12-19 17:11:51,901 # main(): This is RIOT! (Version: 2026.01-devel-290-g56b29-assert/use-config-prefix)
2025-12-19 17:11:51,901 # 0x4025f5 => FAILED ASSERTION.

Note

If testing on native*: In makefiles/arch/native.inc.mk:129 verbose assertions are forced (already in master).

Issues/PRs references

None

[riot-ci]

Murdock results

✔️ PASSED

98879de core/lib: control assert with CONFIG_* macros

Success	Failures	Total	Runtime
10967	0	10968	13m:51s

Artifacts

• Documentation preview