Commit 45b0a2b2 authored by Adam Wujek's avatar Adam Wujek 💬

Kconfig: move asssert to DEVELOPER section

It is enabled by default anyway
Signed-off-by: Adam Wujek's avatarAdam Wujek <adam.wujek@cern.ch>
parent 46b50589
......@@ -21,15 +21,6 @@ config PRINT_BUFSIZE
int
default 128
config ASSERT
bool "Build assertion checks in the code"
default y
help
Build assertions in the code, to catch unexpected situations.
When an assertion fails the code loops over repeating the
error message every second. OTOH, panic() is always built,
with no Kconfig -- and it does the same, unconditionally.
config RAMSIZE
int
default 65536 if WR_SWITCH
......@@ -383,6 +374,16 @@ config PPSI
help
Select this option for the ppsi engine (now only option)
config ASSERT_ENA
bool "Build assertion checks in the code"
depends on DEVELOPER
default y
help
Build assertions in the code, to catch unexpected situations.
When an assertion fails the code loops over repeating the
error message every second. OTOH, panic() is always built,
with no Kconfig -- and it does the same, unconditionally.
config DETERMINISTIC_BINARY
depends on DEVELOPER && EMBEDDED_NODE
boolean "Build a binary that is the same every time"
......@@ -533,3 +534,9 @@ config VLAN_ARRAY_SIZE
default 1
# CONFIG_WR_NODE
config ASSERT
bool
default n if DEVELOPER && !ASSERT_ENA
default y
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment