-
Notifications
You must be signed in to change notification settings - Fork 45
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
ESP-IDF Environment Auto-Loading #49
Comments
It is suppised to download and fetch everything |
I tried again from scratch and it worked when building manually. So it works well when I do the command myself.
Any idea why would this happen? Thank you. |
Yes. When you install the rust compiler using |
If it is not clear what is happening: your shell does have Xtensa clang in your $path, while VScode does not have access to it, because you did not put it in |
Thanks for everything @ivmarkov ! I restarted everything and checked my I am grateful to have all this help. |
Sorry to bother, I am new with those tools.
I previously used ESP-IDF with C. I know we needed to always do a
get_idf
before compiling, but for esp-rs, I thought that given this templates will generate at build a full ESP-IDF environment in the.embuild
it was designed to automatically load the environment when doingcargo build
? (Its a supposition it might not be the case, please let me know).So my question is: Is my setup incorrect, or should we always manually source the
export.sh
file? (Manually doing it would be quite troublesome as when using Rust Analyzer with Flycheck, as they are not in the same env, they would break in VsCode for example and I didn't find yet a workaround).For further information on my issue when launching
cargo check
orcargo build
, here is the output (I think its the usual output for a missing ESP-IDF Python Env, but there might be other information useful if it was supposed to be loaded automatically):Thanks for your help.
The text was updated successfully, but these errors were encountered: