Closed RoscoeTheDog closed 1 year ago
@RoscoeTheDog Could you please upload your project somewhere? As is, there is not enough information provided in this ticket for us to give you some help. It's not clear where the functions like initializeWifi
are defined, whether they have C or C++ linkage, in which component they are located, and so on.
In general, you can also take a look at some of the example projects provided with ESP-IDF. They should demonstrate how to structure the project, splitting it into multiple components. https://github.com/espressif/esp-idf/tree/master/examples/system/console/advanced is one such example.
@RoscoeTheDog Thanks for reporting, would you please help share if any further updates for the issue? Thanks.
Thanks for reporting, will close due to short of feedback, feel free to reopen with more updates. Thanks.
I am using a ESP32-S2 variant for a project in PlatformIO. It seems like the support for this board definition via platformIO is always behind the latest ESPIDF framework updates which is frustrating. Right now it seems as though the basic example for the smartconfig feature no longer sends acknowledgements to the smartphone app. I am trying to rebuild the project purely in ESP-IDF using VScode and the esp-idf extension to see if I can get it working, but it uses a different build system than PlatformIO does and I can't build it.
I understand that CMake wants us to specify what is required dependencies for each component. This seems like a huge huge amount of trouble for me in my instance where I have like 10 headers and source files for each different peripheral on the board I am making use of previously in my platformIO project.
The simplist and sloppiest way I could think of getting everything migrated over was to throw the headers in the main ESP-IDF project folder and tell CMake to look at the same root path for headers like this:
main.c
OUTPUT: