Skip to content

Export ESP_IDF_VERSION in the setup hook - #134

Open
mornepousse wants to merge 1 commit into
mirrexagon:masterfrom
mornepousse:fix-esp-idf-version
Open

Export ESP_IDF_VERSION in the setup hook#134
mornepousse wants to merge 1 commit into
mirrexagon:masterfrom
mornepousse:fix-esp-idf-version

Conversation

@mornepousse

Copy link
Copy Markdown

Fixes #124.

ESP_IDF_VERSION is currently unset in the dev shells, which breaks components
that branch on it — the issue reporter hit this with esp_wifi_remote, where
missing configs make the build fail.

The value is derived the same way ESP-IDF derives it itself, in
tools/idf_tools.py:

match = re.match(r'^v([0-9]+\.[0-9]+).*', idf_version_str)

so major.minor only. That matters: emitting the patch level (5.5.2 rather
than 5.5) would still leave a comparison against the two-part form failing,
which is also the form the reporter says works for them.

Tested on x86_64-linux with esp-idf-full:

$ echo $ESP_IDF_VERSION     # before
$ echo $ESP_IDF_VERSION     # after
5.5

Derived as major.minor, matching ESP-IDF's own tools/idf_tools.py, which
matches '^v([0-9]+\.[0-9]+).*' against version.txt. Components such as
esp_wifi_remote — the Wi-Fi path for the ESP32-P4 — compare against that
two-part form, so emitting the patch level would not help them.

Fixes mirrexagon#124.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ESP_IDF_VERSION environment variable missing

1 participant