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
For cases where users would like to have all of ESP-IDF (the repo itself, GCC toolchain, pip deps) pre-installed - rather than downloaded on-demand during cargo build, it might be useful to have such a command.
The existing alternative is for users to do
git clone --recursive https://github.com/espressif/esp-idf
cd esp-idf
./install.sh esp32
(... and also a few pre-requisites that we don't automate either, as per here).
Not super-difficult, but if we would like to isolate the C world even for offline, such a cargo sub-command might be useful.
The above would just do what we do at build time w.r.t. downloading and installing ESP-IDF.
Given that most of the ESP-IDF download & installation code is in embuild (where cargo espidf itself resides) I don't think that would be such a big lift and shift.
Eventually, we might have an update variant that updates an already existing installation. OR maybe install can do that automatically, if it detects an existing installation.
The text was updated successfully, but these errors were encountered:
For cases where users would like to have all of ESP-IDF (the repo itself, GCC toolchain, pip deps) pre-installed - rather than downloaded on-demand during
cargo build
, it might be useful to have such a command.The existing alternative is for users to do
git clone --recursive https://github.com/espressif/esp-idf cd esp-idf ./install.sh esp32
(... and also a few pre-requisites that we don't automate either, as per here).
Not super-difficult, but if we would like to isolate the C world even for offline, such a cargo sub-command might be useful.
Possible syntax:
The above would just do what we do at build time w.r.t. downloading and installing ESP-IDF.
Given that most of the ESP-IDF download & installation code is in
embuild
(wherecargo espidf
itself resides) I don't think that would be such a big lift and shift.Eventually, we might have an
update
variant that updates an already existing installation. OR maybeinstall
can do that automatically, if it detects an existing installation.The text was updated successfully, but these errors were encountered: