Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
OVMS3-idf/Kconfig

89 lines
2.7 KiB
Text
Raw Normal View History

Initial public version
2016-08-17 15:08:22 +00:00
#
# For a description of the syntax of this configuration file,
# see kconfig/kconfig-language.txt.
#
Standardise remaining uses of SDK to ESP-IDF
2016-08-19 06:30:39 +00:00
mainmenu "Espressif IoT Development Framework Configuration"
Initial public version
2016-08-17 15:08:22 +00:00
menu "SDK tool configuration"
config TOOLPREFIX
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
string "Compiler toolchain path/prefix"
default "xtensa-esp32-elf-"
help
The prefix/path that is used to call the toolchain. The default setting assumes
a crosstool-ng gcc setup that is in your PATH.
Initial public version
2016-08-17 15:08:22 +00:00
config PYTHON
string "Python 2 interpreter"
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
default "python"
help
The executable name/path that is used to run python. On some systems Python 2.x
may need to be invoked as python2.
Initial public version
2016-08-17 15:08:22 +00:00
endmenu
source "$COMPONENT_KCONFIGS_PROJBUILD"
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
menu "Compiler options"
choice OPTIMIZATION_COMPILER
prompt "Optimization Level"
build system: add menuconfig choice for optimization level, reorganize C*FLAGS This change adds two options (Debug/Release) for optimization level. Debug enables -O0, release enables -Os and adds -DNDEBUG (which removes all assert() statements). Debugging symbols are kept in both cases, although we may add an option to strip output file if necessary. Also we used to define all common compiler flags in CPPFLAGS, and then appended them to CFLAGS/CXXFLAGS. It makes it impossible to add preprocessor macros to CPPFLAGS at component level (one has to use CFLAGS/CXXFLAGS instead). Some third party libraries are not compatible with this approach. Changed to the more common way of using these variables.
2016-10-17 04:38:17 +00:00
default OPTIMIZATION_LEVEL_DEBUG
help
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
This option sets compiler optimization level (gcc -O argument).
- for "Release" setting, -Os flag is added to CFLAGS.
build system: fix setting C**FLAGS from project makefile
2016-10-20 09:17:54 +00:00
- for "Debug" setting, -Og flag is added to CFLAGS.
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
"Release" with -Os produces smaller & faster compiled code but it
may be harder to correlated code addresses to source files when debugging.
To add custom optimization settings, set CFLAGS and/or CPPFLAGS
in project makefile, before including $(IDF_PATH)/make/project.mk. Note that
custom optimization levels may be unsupported.
build system: add menuconfig choice for optimization level, reorganize C*FLAGS This change adds two options (Debug/Release) for optimization level. Debug enables -O0, release enables -Os and adds -DNDEBUG (which removes all assert() statements). Debugging symbols are kept in both cases, although we may add an option to strip output file if necessary. Also we used to define all common compiler flags in CPPFLAGS, and then appended them to CFLAGS/CXXFLAGS. It makes it impossible to add preprocessor macros to CPPFLAGS at component level (one has to use CFLAGS/CXXFLAGS instead). Some third party libraries are not compatible with this approach. Changed to the more common way of using these variables.
2016-10-17 04:38:17 +00:00
config OPTIMIZATION_LEVEL_DEBUG
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
bool "Debug (-Og)"
build system: add menuconfig choice for optimization level, reorganize C*FLAGS This change adds two options (Debug/Release) for optimization level. Debug enables -O0, release enables -Os and adds -DNDEBUG (which removes all assert() statements). Debugging symbols are kept in both cases, although we may add an option to strip output file if necessary. Also we used to define all common compiler flags in CPPFLAGS, and then appended them to CFLAGS/CXXFLAGS. It makes it impossible to add preprocessor macros to CPPFLAGS at component level (one has to use CFLAGS/CXXFLAGS instead). Some third party libraries are not compatible with this approach. Changed to the more common way of using these variables.
2016-10-17 04:38:17 +00:00
config OPTIMIZATION_LEVEL_RELEASE
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
bool "Release (-Os)"
build system: add menuconfig choice for optimization level, reorganize C*FLAGS This change adds two options (Debug/Release) for optimization level. Debug enables -O0, release enables -Os and adds -DNDEBUG (which removes all assert() statements). Debugging symbols are kept in both cases, although we may add an option to strip output file if necessary. Also we used to define all common compiler flags in CPPFLAGS, and then appended them to CFLAGS/CXXFLAGS. It makes it impossible to add preprocessor macros to CPPFLAGS at component level (one has to use CFLAGS/CXXFLAGS instead). Some third party libraries are not compatible with this approach. Changed to the more common way of using these variables.
2016-10-17 04:38:17 +00:00
endchoice
assertions: Add "silent" option Reduces assertion codesize overhead by approximately 35%
2017-07-12 04:57:44 +00:00
choice OPTIMIZATION_ASSERTION_LEVEL
prompt "Assertion level"
default OPTIMIZATION_ASSERTIONS_ENABLED
help
Assertions can be:
- Enabled. Failure will print verbose assertion details. This is the default.
- Set to "silent" to save code size (failed assertions will abort() but user
needs to use the aborting address to find the line number with the failed assertion.)
- Disabled entirely (not recommended for most configurations.) -DNDEBUG is added
to CPPFLAGS in this case.
config OPTIMIZATION_ASSERTIONS_ENABLED
prompt "Enabled"
bool
help
Enable assertions. Assertion content and line number will be printed on failure.
config OPTIMIZATION_ASSERTIONS_SILENT
prompt "Silent (saves code size)"
bool
help
Enable silent assertions. Failed assertions will abort(), user needs to
use the aborting address to find the line number with the failed assertion.
config OPTIMIZATION_ASSERTIONS_DISABLED
prompt "Disabled (sets -DNDEBUG)"
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
bool
help
assertions: Add "silent" option Reduces assertion codesize overhead by approximately 35%
2017-07-12 04:57:44 +00:00
If assertions are disabled, -DNDEBUG is added to CPPFLAGS.
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
assertions: Add "silent" option Reduces assertion codesize overhead by approximately 35%
2017-07-12 04:57:44 +00:00
endchoice # assertions
build system: Split setting of compiler optimisation level from assertions on/off
2017-06-19 01:25:45 +00:00
endmenu # Optimization level
Initial public version
2016-08-17 15:08:22 +00:00
menu "Component config"
source "$COMPONENT_KCONFIGS"
endmenu
Reference in a new issue Copy permalink