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
There's a reference to a truncated commit heads/idf-release/v4.4-0-gd3340 in the esp_app_desc_t but that doesn't appear to be published anywhere.
The build scripts in https://github.com/espressif/esp32-arduino-lib-builder always use the latest branch for some of the dependencies (e.g. components/arduino_tinyusb/tinyusb). There's no information on which commits of these were used to build the 2.0.3 release.
This makes it very difficult to make one change to the sdkconfig and rebuild without making other changes (assuming the code is even still compatible across all of the dependencies).
I have checked existing issues, online documentation and the Troubleshooting Guide
I confirm I have checked existing issues, online documentation and Troubleshooting guide.
The text was updated successfully, but these errors were encountered:
Every time me-no-dev commits a new version of IDF (eg #6594), he indicates which versions of the components were used. AFAIK the daily CI stuff uses whatever is master in each of those sources. For release versions, look for the last IDF commit in the release notes, which will have the list of the necessary components.
Version
v2.0.3
Description
It looks like https://github.com/espressif/esp32-arduino-lib-builder is used to build the contents of
tools/sdk/
but there's no information on which commit in that repository was used.There's a reference to a truncated commit
heads/idf-release/v4.4-0-gd3340
in theesp_app_desc_t
but that doesn't appear to be published anywhere.The build scripts in https://github.com/espressif/esp32-arduino-lib-builder always use the latest branch for some of the dependencies (e.g.
components/arduino_tinyusb/tinyusb
). There's no information on which commits of these were used to build the 2.0.3 release.This makes it very difficult to make one change to the
sdkconfig
and rebuild without making other changes (assuming the code is even still compatible across all of the dependencies).I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: