zephyr
/
esp-idf
mirror of https://github.com/zephyrproject-rtos/esp-idf.git
1
0
Fork 0
Code Issues Releases Wiki Activity
esp-idf/Kconfig

49 lines
1.3 KiB
Plaintext
Raw Normal View History

Initial public version
2016-08-17 17:08:22 +02: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 08:30:39 +02:00
mainmenu "Espressif IoT Development Framework Configuration"
Initial public version
2016-08-17 17:08:22 +02: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 07:24:58 +02: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 17:08:22 +02: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 07:24:58 +02: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 17:08:22 +02:00
endmenu
source "$COMPONENT_KCONFIGS_PROJBUILD"
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 06:38:17 +02:00
choice OPTIMIZATION_LEVEL
prompt "Optimization level"
default OPTIMIZATION_LEVEL_DEBUG
help
build system: use -Og instead of -O0 for debug builds, expand help text in menuconfig
2016-10-20 10:10:51 +02:00
This option sets optimization level.
build system: fix setting C**FLAGS from project makefile
2016-10-20 11:17:54 +02:00
- for "Release" setting, -Os flag is added to CFLAGS,
build system: use -Og instead of -O0 for debug builds, expand help text in menuconfig
2016-10-20 10:10:51 +02:00
and -DNDEBUG flag is added to CPPFLAGS.
build system: fix setting C**FLAGS from project makefile
2016-10-20 11:17:54 +02:00
- for "Debug" setting, -Og flag is added to CFLAGS.
To override any of these settings, set CFLAGS and/or CPPFLAGS
in project makefile, before including $(IDF_PATH)/make/project.mk.
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 06:38:17 +02:00
config OPTIMIZATION_LEVEL_DEBUG
bool "Debug"
config OPTIMIZATION_LEVEL_RELEASE
bool "Release"
endchoice
Initial public version
2016-08-17 17:08:22 +02:00
menu "Component config"
source "$COMPONENT_KCONFIGS"
endmenu