cmake build error #2286
Comments
Thanks for reaching out to us and apologies for the delay. We wanted to follow up with some clarifying questions to help you better.
Please get back to us with the requested details so that we can help you further. |
Hello @ivopashov, I am able to reproduce this issue when the environment variable IDF_PATH has a value. Can you use the following command to confirm IDF_PATH is left undefined?
If this command returns a value please enter Thanks |
Hello @ivopashov, I am going to resolve this issue with the hope that it was resolved. Please re-open this issue in case you are having any more trouble building Espressif with CMake |
Sorry for not replying in timely manner. @leegeth, i am using the quick connect flow so i am not downloading the repo from Github . @lundinc2 i know about this variable and it does not have value.
However, i managed to build the thing from the repository. I am experiencing issues with the QUICK CONNECT flow only. |
@ivopashov can you use the repository in the meantime? I believe there is some issue with the quick connect build on Espressif. |
@lundinc2 Yes, I am good using the repo. Yhat's the path I took. |
@ivopashov can you post what version of FreeRTOS you downloaded from the console, and what the configuration was? Thanks |
@ivopashov One thing the call out, the path cannot contain spaces, otherwise I espressif build will fail. Try to remove the space in your path, |
Describe the bug
I am trying to build FreeRTOS on a esp32 devkit-c device but hit a build error. Here is what i do:
I guess
xtensa-esp32-elf-gcc -> 5.2.0
is compatible withesp-idf -> 3.3
as this is what espressif provide for that version.3.13
):FreeRTOS 2
in my case) and firecmake -DVENDOR=espressif -DBOARD=esp32_wrover_kit -DCOMPILER=xtensa-esp32 -S . -B my-build-directory
and the
CMakeError.log
outputSomething leads me to believe it is some version mismatch but this environment is quite new for me and am having issue to grasp what the real problem is.
I am using these aws docs.
System information
git describe --tags
to find it)Code to reproduce the bug
.Expected behavior
I expect error free build.
The text was updated successfully, but these errors were encountered: