Working with ESP-IDF in CLion · Developer Portal

[giscus[bot]]

Working with ESP-IDF in CLion · Developer Portal

The developer resources in just one place!

https://developer.espressif.com/blog/clion/

[ctag-fh-kiel]

Great tutorial!
When starting debug on esp32s3, however, breakpoints don't work right away. For me they become active only after turning them off an on again once the debugger is running. Any idea why?

[olegznv]

Thank you for your feedback! Sorry for the late reply, I just noticed your question.

My colleagues and I haven’t encountered this issue. So, it’s worth investigating it. Could you please reproduce the issue and collect logs with Help | Collect Logs and Diagnostic Data. Then, create a ticket in our issue tracker and attach the logs. The team will look into it.

If you are unfamiliar with YouTrack, see the How to follow YouTrack issues and receive notifications article.

[AbdusSamadTariq]

When following all the steps until step 7 in confugration on a windows machine I get the following error:

"C:\Program Files\JetBrains\CLion 2025.1.1\bin\cmake\win\x64\bin\cmake.exe" -DCMAKE_BUILD_TYPE=Debug "-DCMAKE_MAKE_PROGRAM=C:/Program Files/JetBrains/CLion 2025.1.1/bin/ninja/win/x64/ninja.exe" -DIDF_TARGET=esp32 -G Ninja -S C:\Espressif\frameworks\esp-idf-v5.4.1\examples\get-started\hello_world -B C:\Espressif\frameworks\esp-idf-v5.4.1\examples\get-started\hello_world\build
-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.49.0.windows.1")
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- The ASM compiler identification is unknown
-- Found assembler: xtensa-esp32-elf-gcc
CMake Error at C:/Espressif/frameworks/esp-idf-v5.4.1/tools/cmake/project.cmake:571 (__project):
The CMAKE_C_COMPILER:

xtensa-esp32-elf-gcc

is not a full path and was not found in the PATH. Perhaps the extension is
missing?

Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
CMakeLists.txt:6 (project)

CMake Error at C:/Espressif/frameworks/esp-idf-v5.4.1/tools/cmake/project.cmake:571 (__project):
The CMAKE_CXX_COMPILER:

xtensa-esp32-elf-g++

is not a full path and was not found in the PATH. Perhaps the extension is
missing?

Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
CMakeLists.txt:6 (project)

CMake Error at C:/Espressif/frameworks/esp-idf-v5.4.1/tools/cmake/project.cmake:571 (__project):
The CMAKE_ASM_COMPILER:

xtensa-esp32-elf-gcc

is not a full path and was not found in the PATH. Perhaps the extension is
missing?

Tell CMake where to find the compiler by setting either the environment
variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
Call Stack (most recent call first):
CMakeLists.txt:6 (project)

-- Warning: Did not find file Compiler/-ASM
-- Configuring incomplete, errors occurred!

[Finished]

How do I fix this?

[elmot]

It looks like either ESP-IDF tools are not installed properly, environment script is not taken into use, or it does not work properly
Please verify the tools existense, the script path, the toolchain name. If .bat script does not work, try .ps1
If nothing happens, try to run esp-idf build without CLion

[AbdusSamadTariq]

You are absolutely correct! I encountered an issue where the export.bat script failed to execute as expected. This was due to the Windows installer for ESP-IDF not providing the most up-to-date Python environment required by the IDF tools.

To resolve this, I bypassed the installer and instead cloned the ESP-IDF repository directly from its Git source. Following the manual setup instructions, I then installed the necessary Python environment and dependencies. This approach successfully rectified the issue, allowing all subsequent ESP-IDF operations to function correctly.

[VictorManoel]

I'm new to using clion and esp32, but if I open the examples directory, won't it end up changing the code in the examples? And how do I open a new project without being one of the examples?

[elmot]

And how do I open a new project without being one of the examples?

idf.py create-project <name>

or choose an example and then create a project out of it