ESP-IDF
ESP-IDF is the official development framework for the ESP32 and ESP32-S Series SoCs. This article is an introductory guide for working with ESP-IDF in CLion.
Some steps replicate the ESP-IDF Get Started guide. Examples below are given for the case of macOS, Windows-specific instructions are marked accordingly.
Prepare the environment
Make sure you have a recent Python version, pip, and git installed on your system.
Using your system terminal, create a directory for ESP-IDF and clone the official repository:
mkdir -p ~/esp cd ~/esp git clone --recursive https://github.com/espressif/esp-idf.gitESP-IDF will be downloaded into ~/esp/esp-idf.
In the same shell, install the tools:
cd esp-idf ./install.shOn Windows, make sure the USB bridge of the ESP-32 board is identified correctly. You can check that in the Device Manager.
Set up a sample project using CLion's terminal
In CLion, go to and select the ~/esp/esp-idf directory.
At this point, project loading might fail due to the Current directory '../esp/esp-idf' is not buildable... error.
Open CLion's built-in terminal ( or Alt+F12).
Set up the environment variables by running
. $HOME/esp/esp-idf/export.sh:
Let's configure the hello_world project from the examples/get-started directory. The following commands set ESP32 chip as the target and run the menuconfig configuration utility:
cd $IDF_PATH/examples/get-started/hello_world idf.py set-target esp32 idf.py menuconfigThe last command opens the configuration menu. As the hello_world project we are using will run with default configuration, you don't need to set it up in this menu.
Step out from the menu, and check the configuration is complete.
Now we can build hello_world by running
idf.py build:
Next up, you can continue working with the project in CLion using the terminal. This will not require additional CMake configuration. Alternatively, you can set up CMake so that the project can be loaded, built and run without the command line (see below).
Configure an ESP CMake project in CLion
Open the Hello-world project
Go to and select the esp/esp-idf/examples/get-started/hello_world folder.
Click Open as Project and trust the sources.
At this point, project loading might fail.
Toolchain on Windows
On Windows, go to and configure a toolchain for your project. See Tutorial: Configure CLion on Windows for instructions.
Source the environment (macOS)
Go to .
Click Add environment next to the Name field, then click From file.
Navigate to esp/esp-idf and select export.sh:
Save the toolchain settings.
The project will be reloaded automatically. In case of errors, call from the main menu.
Source the environment using a custom script (Windows)
On Windows, two files are required to set up the ESP-IDF environment. To automate this, you can create a simple script that will load them both and use it as the toolchain environment file.
Create a script file in the project folder. For example, espdif_source.bat.
Customize the following lines and add them to your script:
@call C:\Espressif\python_env\idf5.0_py3.8_env\Scripts\activate.bat @call C:\Espressif\frameworks\esp-idf-v5.0-2\export.batGo to .
Click Add environment next to the Name field, then click From file.
Select the newly created file.
Save the toolchain settings.
The project will be reloaded automatically. In case of errors, call from the main menu.
Build the project
CLion will automatically create run/debug configurations for all the detected CMake targets.
To build the project, select app in the configuration switcher, then click the hammer icon or press Ctrl + F9 to run build for this configuration.
At this point, all CLion code insight features are available for your ESP project. Watch Developing for ESP32 With CLion on Windows: Code insight for some examples.
Flashing and monitoring an ESP-32 chip in CLion
Select flash in the configuration switcher and click the hammer icon or press Ctrl + F9 to build it.
In the build output, you can check the percentage indicator for chip flashing.
Select the monitor configuration and build it. If you get an error that serial port can not be opened, then do the following:
Open the Device Manager and check the port that is used by your ESP device.
Add one more variable to the Environment variables in CMake settings:
ESPPORT. Set the value to the port, for example,COM3.After the project is reloaded, build the monitor configuration again. The ESP-32 chip should report back as expected.
Known issues and limitations
There's a feature request for the ability to initialize toolchain environment via a script.
Currently, the size of
longis considered 64-bit, while there should be 32-bit for ESP-32 (CPP-23731). To workaround this, go to and add--target=riscv32to the clangd diagnostics options.
Troubleshooting (Windows)
If you are getting the Git executable not found error on Windows, make sure that Git is installed into a location discoverable by ESP-IDF's find_package(Git) command.
To workaround that, add the GIT environment variable with the full path to the git.exe binary. You can do that by modifying esp/idf/tools/cmake/git_submodules.cmake. In the first line, change find_package(Git) to the following: