Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement cargo espidf install #338

Open
ivmarkov opened this issue Sep 15, 2024 · 0 comments
Open

Implement cargo espidf install #338

ivmarkov opened this issue Sep 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ivmarkov
Copy link
Collaborator

ivmarkov commented Sep 15, 2024

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:

cargo espidf install [--idf-ver <branch-or-tag>] [--tooling-mcu <esp32|esp32c3|...|all>]

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

1 participant