-
Notifications
You must be signed in to change notification settings - Fork 53
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
Project generated do not build when normal esp-idf environment is sourced #204
Comments
See #188 (comment) |
I Just installed v5.1 and it still doesnt work.
|
esp-idf uses a specifc set of tools -> cmake, ninja, riscv-gcc , xtensa-gcc. When you install a specifc version of esp-idf via the python install scripts it also should install all this tools. In a fully managed esp-idf repo ( auto installed by us if no activated esp-idf env found) we install this tools for you inside the .embuild dir for the respected esp-idf version. It looks like your install is missing ninja so that's why it seams to fail. You don't have this env variable set right? |
So I have been digging some more, It turned out the problem was that I was working in a terminal where i had already sourced the environment for a normal esp idf environment. It would be great if the environments sourced would "deactivate" then other environment |
Technically it should be able to use the "other" sourced environment if it is setup with all the tools needed. The build script is activity trying to do so, but again in this case seams to stumble onto a maybe not fully installed ninja in your "other" environement? |
@PocketPi What is the OS and hardware of the host where you are compiling? |
ubuntu 23.10 and its an intel cpu |
@PocketPi i think your the PATH variables emitted in your setup aren't quite right. Besides your activated sourced esp-idf install in "/home/peter/data/tools/esp-idf-v5.1" there are also traces for "/home/peter/.espressif/tools/", and last but not least the path to the ninja tool is even completely off as by default it should not check in "/home/peter/.local/bin/ninja". Did you manually install it there and then remove it or something? Also be aware that esp-idf v5.1 is using gcc12 while v5.2 is using gcc13. So its crucial that your tools dir is clean. |
closing this for now as i outlined what the problem was. In general we recommend to either only use exactly one external activated env, or use our managed installs. Our managed installs don't permanently change env vars and so can't create this issues. And if you are using a single external activated env, through the official script the impact also should be limted. In any case keep your env vars clean. |
Bug description
I have esp-idf v5.2.1 installed as im using that for my main project. I have now tried to make a rust project off the template but that do not build. This is what i get from the build process:
To Reproduce
Steps to reproduce the behavior:
Environment
setup as described in this guide: https://github.com/esp-rs/esp-idf-template?tab=readme-ov-file#prerequisites
The text was updated successfully, but these errors were encountered: