-
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
error: failed to run custom build command for esp-idf-sys v0.33.1
#130
Comments
Hmm, the output does not contain the If that turns out to be the culprit, I strongly recommend moving to WSL2 (or somehow living with short project name in the drive root). |
Do I need to enable something to see
|
The output from the failed build is too short. Are you sure this is all of it? |
Well, I cleaned it and built it again. If I don't need to enable something to see more of the output then I guess that's it. I also tried to manually install
|
OK, one last try:
|
I have Python 3.10.11 (default) and 3.11.4. Apparently, Python 3.10.11 is not very descriptive and setting
I have additional files in .embuild directory that weren't generating before so I guess changing Python version allowed me to progress further. |
Let me start with the TL;DR: The problem is that the
That's weird. It might be that you need some additional dependency that is not on your system, hence the lib fails to load. Another reason might be that you are running a 32 bit system while the lib is 64 bit, or the other way around. Guessing here. You might try to down-grade the ESP toolchain installed by As for the other things you mentioned:
|
Okay, I managed to build it. Turns out I needed to add clang.exe to
As for the error log, I assure you that when I was using Python 3.10.11 there was no |
Which |
I used |
Then check the environment variables |
After reinstalling
|
Have you tried restarting the terminal between installation and project compilation? |
Yes, I have restarted the terminal after installation. The strange thing about it is that after echoing the environmental variables are set correctly according to |
So, if I understood correctly:
Is my understanding correct? Which VsCode terminal are you using? |
So before I run/build the template and before I run I checked out environmental variables through the GUI app provided by Windows and by the looks of it the variables are set for the current user(me), but aren't set for all users. I think in order for the environmental variables to be visible during building they need to be set globally for all users.
I used VS Code's |
Just to confirm, you are echoing the variables in the same terminal as you are running
Can you check what happens when you source the export file? I'd guess that they are only set for current user. I will try to reproduce the error |
I did some investigations, after running |
@SergioGasquez I'm not sure whether the above visual location in the latest Windows incarnation you are mentioning is for "system" or "user" environment variables, as somehow the wording mentions both. In any case:
This:
... is not correct. And we should - again - not do any system-wide changes. |
@SergioGasquez Some more suggestions:
|
... and we should shuffle our |
Correct.
I'm not sure what you mean by this
On what terminal did you try to execute it? In
Well, today (after restarting my PC) when I tried building the template I was greeted with this error: |
I don't have a hard opinion on this regard, but this was discussed in the past, and we decided that on Windows we would modify the Ideally, once we can use LLD as linker, this problem will disappear (we would only require setting
I was using powershell.
Not sure why your environment changes this way. I was able to build projects in Windows with no issue |
I don't remember the discussion, but regardless, I keep noticing folks routinely forget to call the script. And was showing evidence, that other tooling on Unix bravely touches Also - and hopefully - even if the path is modified by sourcing the |
Closing in favor of esp-rs/esp-idf-hal#319 |
Bug description
I tried building unmodified esp-idf-template using cargo. I believe all prerequisites listed in README.md are installed correctly.
Environment
The text was updated successfully, but these errors were encountered: