esp-idf/Kconfig

#
# For a description of the syntax of this configuration file,
# see kconfig/kconfig-language.txt.
#
mainmenu "Espressif IoT Development Framework Configuration"


menu "SDK tool configuration"
config TOOLPREFIX
    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.

config PYTHON
    string "Python 2 interpreter"
    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.
endmenu

source "$COMPONENT_KCONFIGS_PROJBUILD"

menu "Compiler options"

choice OPTIMIZATION_COMPILER
    prompt "Optimization Level"
    default OPTIMIZATION_LEVEL_DEBUG
    help
        This option sets compiler optimization level (gcc -O argument).

        - for "Release" setting, -Os flag is added to CFLAGS.
        - for "Debug" setting, -Og flag is added to CFLAGS.

        "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.

config OPTIMIZATION_LEVEL_DEBUG
    bool "Debug (-Og)"
config OPTIMIZATION_LEVEL_RELEASE
    bool "Release (-Os)"
endchoice

config OPTIMIZATION_ASSERTIONS
    prompt "Enable assertions"
    bool
    default y
    help
        Enable assertions.

        If disabled, -DNDEBUG is added to CFLAGS.

endmenu # Optimization level

menu "Component config"
source "$COMPONENT_KCONFIGS"
endmenu
Initial public version 2016-08-17 11:08:22 -04: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 02:30:39 -04:00			`mainmenu "Espressif IoT Development Framework Configuration"`
Initial public version 2016-08-17 11:08:22 -04: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 01:24:58 -04: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 11:08:22 -04: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 01:24:58 -04: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 11:08:22 -04:00			`endmenu`

			`source "$COMPONENT_KCONFIGS_PROJBUILD"`

build system: Split setting of compiler optimisation level from assertions on/off 2017-06-18 21:25:45 -04: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 00:38:17 -04:00			`default OPTIMIZATION_LEVEL_DEBUG`
			`help`
build system: Split setting of compiler optimisation level from assertions on/off 2017-06-18 21:25:45 -04: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 05:17:54 -04:00			`- for "Debug" setting, -Og flag is added to CFLAGS.`
build system: Split setting of compiler optimisation level from assertions on/off 2017-06-18 21:25:45 -04: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 00:38:17 -04:00			`config OPTIMIZATION_LEVEL_DEBUG`
build system: Split setting of compiler optimisation level from assertions on/off 2017-06-18 21:25:45 -04: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 00:38:17 -04:00			`config OPTIMIZATION_LEVEL_RELEASE`
build system: Split setting of compiler optimisation level from assertions on/off 2017-06-18 21:25:45 -04: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 00:38:17 -04:00			`endchoice`

build system: Split setting of compiler optimisation level from assertions on/off 2017-06-18 21:25:45 -04:00			`config OPTIMIZATION_ASSERTIONS`
			`prompt "Enable assertions"`
			`bool`
			`default y`
			`help`
			`Enable assertions.`

			`If disabled, -DNDEBUG is added to CFLAGS.`

			`endmenu # Optimization level`

Initial public version 2016-08-17 11:08:22 -04:00			`menu "Component config"`
			`source "$COMPONENT_KCONFIGS"`
			`endmenu`