Closed AirWind001 closed 1 year ago
Not sure if this is a bug or a general pathing issue, but have the same problem with any files that used to be in the framework-espidf/components/driver/include directory. The header files all seem to be in the framework-espidf/components/driver/include/driver directory. I can't figure out how to get the compiler to look in the driver/include/driver directory. I can copy the files back to the driver directory and/or the driver/include directory and it all compiles, but this is not a solution going forward.
Uninstall and clean reinstall fixes the issue
I tried reinstalling esp-idf and it did nothing. Some of my includes work, but some don't. Currently I'm stuck on the esp_tls.h even though the folder is right there next to other components that I cán include..
I can manually add the path to my cmakelists, but I'd have to do that manually for about a third of all the components.. It seems completely random which includes it will accept and which it will simply spit out
@Aecnoril have you added esp_tls component to REQUIRES or PRIV_REQUIRES list in your CMakeLists.txt?
Answers checklist.
IDF version.
IDFv4.4
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
build successfully
What is the actual behavior?
fatal error: driver/temperature_sensor.h: No such file or directory
Steps to reproduce.
Build or installation Logs.
More Information.
I'm trying to run an example code that's present on idf v5.0 on my toolchain which is v4.4 because the example file from v4.4 doesn't support esp32s3. same error when setting the target to esp32-s2.