The xtensa-files are then installed in this directory: /Users//.espressif/tools/xtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin. I want to mention that it is necessary to create the ~/esp folder first when using the standard toolchain, because otherwise all the commands from the documentation don't work. I deleted all the files and started from scratch again. I think the error was caused by installing the newest IDF (4.2) with an older version (3.2.2) of the toolchain. Toolchain.png (72.85 KiB) Viewed 8380 times CMake.png (101.94 KiB) Viewed 8380 times It is probably easy to fix, but I'm stuck at the moment and can't find a solution. To the compiler, or to the compiler name if it is in the PATH.
#How to use clion full
Variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
Tell CMake where to find the compiler by setting either the environment Is not a full path and was not found in the PATH. The ASM compiler identification is unknownĪnd a CMake Error for each compiler like this one: The CXX compiler identification is unknown The C compiler identification is unknown When loading the hello_world project into CLion I am getting the message: I added the IDF_PATH/ PATH in the environment table + CMake options and I linked the toolchain as you can see on the attachments. Has anybody some advice to make it running and can explain which settings in the Preferences menu are necessary? I installed everything as written in the ESP-IDF documentation on macOS and it works running the terminal. I am trying to use the ESP-IDF with CLion, but I have some problems with the configuration.
0 kommentar(er)
