You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the external platform feature, there are some wrong include directives that lookup to the default ESP32 platform and not to the custom external platform defined.
The wrong includes are in the following files:
In all these files there is the static path #include <platform/ESP32/xxxxxx> but it's not correct when using the external platform.
In components/esp_matter/esp_matter_ota.h for example the include is:
#include <platform/ESP32/OTAImageProcessorImpl.h>
but the path platform/ESP32 should not be static but dynamic because I'm using the external platform where the platform path is different (platform/ESP32_custom in my case).
In this way it does not compile my custom code implementation but the default implementation defined in platform/ESP32.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Wrong include paths when using the external platform feature
Wrong include paths when using the external platform feature (CON-1607)
Mar 20, 2025
When using the external platform feature, there are some wrong include directives that lookup to the default ESP32 platform and not to the custom external platform defined.
The wrong includes are in the following files:
In all these files there is the static path
#include <platform/ESP32/xxxxxx>
but it's not correct when using the external platform.In
components/esp_matter/esp_matter_ota.h
for example the include is:#include <platform/ESP32/OTAImageProcessorImpl.h>
but the path
platform/ESP32
should not be static but dynamic because I'm using the external platform where the platform path is different (platform/ESP32_custom
in my case).In this way it does not compile my custom code implementation but the default implementation defined in
platform/ESP32
.The text was updated successfully, but these errors were encountered: