600c8f7d85
This patch does several things, most notably it changes the semantics
of CONFIG_DEBUG. CONFIG_DEBUG continues to behave as a vaguely defined
"debug mode" that enables printf's, -Og, etc. but now the user may
choose to be in "debug mode" while using a different optimization
level than -Og.
Tp support this a new config is defined to enable -Og;
CONFIG_DEBUG_OPTIMIZATIONS.
Additionally CONFIG_SIZE_OPTIMIZATIONS is introduced to allow the user
to explicitly request optimizing for size instead of relying on
defaulting to it.
The three config's {NO,SIZE,DEBUG}_OPTIMIZATIONS are now organized in
a Kconfig choice to ensure that at most one can be enabled at a time.
Finally, selected users of CONFIG_DEBUG have been ported to use one of
the optimizations configs when it was clear from usage that the
intention was to behave differently when using a different
optimization level and not when in "debug mode".
Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
36 lines
820 B
Plaintext
36 lines
820 B
Plaintext
#
|
|
# Copyright (c) 2016 Intel Corporation
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
|
|
menu Testing
|
|
|
|
source "tests/ztest/Kconfig"
|
|
|
|
config TEST
|
|
bool "Mark project as a test"
|
|
default n
|
|
select COVERAGE if NATIVE_APPLICATION
|
|
help
|
|
Mark a project or an application as a test. This will enable a few
|
|
test defaults.
|
|
|
|
config TEST_EXTRA_STACKSIZE
|
|
int "Test function extra thread stack size"
|
|
default 0
|
|
default 768 if XTENSA
|
|
help
|
|
Additional stack for tests on some platform where default is not
|
|
enough.
|
|
|
|
config COVERAGE
|
|
bool "Create coverage data"
|
|
depends on NATIVE_APPLICATION
|
|
default n
|
|
help
|
|
This option will build your application with the -coverage option
|
|
which will generate data that can be used to create coverage reports.
|
|
Currently this is fully supported only on the native POSIX port.
|
|
endmenu
|