Project Configuration Guide

This guide is intended to describe three aspects of project configuration in ESP-IDF:

  • How the configuration can be edited (idf.py menuconfig and configuration via plugins)

  • How to use configuration values in C code and CMake

  • How to define new configuration options for the project

Editing the Configuration

As mentioned in the Project Configuration, values currently assigned to the configuration options are stored in the sdkconfig file. This file should not be edited manually, because there can be relationships between the configuration options that could be broken by manual editing. Instead, the idf.py menuconfig command (or its alternatives depending on the specific IDE used) should be used.

If the user wants to redefine the default values of the configuration options set in Kconfig files, the sdkconfig.defaults file can be used. The values set there overwrite those from Kconfig files, but user can still change those via idf.py menuconfig. Those user-set values for the configuration options will be stored in the sdkconfig file, sdkconfig.defaults will remain unchanged.

There are several ways how to configure the project, depending on the IDE used. The most common way is to use the idf.py menuconfig command. This command opens a TUI (Text-based User Interface) where user can set the configuration options. The configuration is saved into the sdkconfig file. Alternatively, IDE plugins can be used as well.

Independently on the tool used, configuration values are loaded in the following order, values from later steps may override those from previous ones. These steps are done automatically and are described here only in order to explain the behavior:

  1. Default configuration option values from Kconfig files are loaded, together with the relationships between them.

  2. If sdkconfig.defaults file is found, default values from this file are loaded.

  3. If present, sdkconfig file is loaded.

When the configuration is saved, the values in the sdkconfig file are updated, as well as those in sdkconfig.h, sdkconfig.cmake and sdkconfig.json.

Configuration with idf.py menuconfig

Using the idf.py menuconfig command in terminal or command line is the most system and IDE agnostic way of configuration. This command opens a TUI (Text-based User Interface) where user can set the configuration options. Navigation is realized by arrow keys, other hotkeys are described in the lower part of the window.

../../_images/menuconfig-screen.png

Configuration with ESP-IDF Plugin for Visual Studio Code

After successful installation of the ESP-IDF plugin for Visual Studio Code, follow their Basic Use document and search for the Configuration Editor option.

Configuration with ESP-IDE

We also provide plugin for Eclipse IDE. To edit the project configuration, follow our documentation about SDK configuration

Note

If you are using another IDE/plugin, please refer to the documentation of the IDE/plugin or use command line command idf.py menuconfig.

How to Use Configuration Variables in C Code and CMake

When the configuration is being saved to sdkconfig file, it is also saved in several different formats, including sdkconfig.h and sdkconfig.cmake. The values in these files can be used in C code and CMake scripts.

Example of using configuration options in C code:

// Contents of sdkconfig.h file (generated automatically, it should NOT be changed manually)
//(...)
#define CONFIG_USE_WARP 1
#define CONFIG_WARP_SPEED 42
//(...)

// Contents of C code file
#include "sdkconfig.h"
(...)
#if CONFIG_USE_WARP
    set_warp_speed(CONFIG_WARP_SPEED);
#else
    set_warp_speed(0);
#endif

Example of using configuration options in CMake script:

# Contents of sdkconfig.cmake file (generated automatically, it should NOT be changed manually)
#(...)
set(CONFIG_USE_WARP 1)
set(CONFIG_WARP_SPEED 42)
#(...)

# Contents of CMakeLists.txt file
#(...)
if(CONFIG_USE_WARP)
    set(WARP_SPEED ${CONFIG_WARP_SPEED})
else()
    set(WARP_SPEED 0)
endif()
#(...)

Defining New Configuration Options for the Project

Some applications can get very complex and require a lot of configuration options. In such cases, it is useful to define new configuration options for the project. Similar to components, the application can have its own configuration options. These options are defined in the Kconfig or Kconfig.projbuild file in the main folder of the project. The process is the same as defining new configuration options for components, only with different location location of the Kconfig or Kconfig.projbuild file (main instead of the root folder).

Was this page helpful?