-
Notifications
You must be signed in to change notification settings - Fork 316
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 on build in version 0.2.1 (VSC-316) #93
Comments
Hi. I have noticed same issue. In my case, error only is shown if I open GUI configuration tool. Everytime I open it, change any parameter and click on save, when I try to build and upload firmware with new changes, @mvacha error is shown too. If I restart vscode, upload works again without problem. However, if I open GUI configuration tool again, error appears again, so it seems problem is related with GUI tool. Regards. |
@jmpmscorp are you also facing the problem on a windows machine ? |
Hi @SoumeshBanerjee. Yes, my machine has Windows 10 version. If you need, I can test it with an Ubuntu 20.04 virtual machine I have mounted with vscode and different esp-idf framework version. Edit: I forgot it. In my Windows I am working with release/4.1 branch. |
Sure, Thanks |
Hi again @SoumeshBanerjee . Tested with Ubuntu 20.04. No error is shown. |
@jmpmscorp Thanks
Same for my case no error on Mac and Linux; once I have access to the windows machine/vm will test this problem and let you guys know Thanks for reporting and helping |
Having the same issue after the ESP-IDF extension updated.
|
After you install the extension and run the onboarding page this error happens. Have anyone tried closing vscode and reopen it and see if they can build ? |
@brianignacio5 yes, this usually fixed the issue, but it was not a reliable "fix". E.g. opening a second instance of VS Code would trigger this bug again. After downgrading to 0.20 I've never experienced this bug again. |
I only managed to reproduce on Win 10 VM on first install, probably buildManager is not getting the new values right away but after vscode restart it works ok. Haven't been able to reproduce this after for example on multiple opened vscode windows. Tested on Windows 10 Version 1909 Build 18363 on VMWare 10.1.6 VM running in Mac OS Catalina Could you please check if there was any error during IDF Onboarding and the values in In any case, there is a probable fix in #95 |
i got this error now.. its all the time i cannot build from the build ICON on the bottom bar anymore no errors during onboarding... confirmed downgraded to v0.2.0, build on the bottom bar works perfectly. |
I've tried a restart of VSCode and Windows, no changes. When looking at "idf.customExtraPaths" and "idf.espIdfPath" I see a mixed usage of "\" (backslash) and "\\" (double backslash) and some single slashes "/". What would be the correct thing?
|
@brianignacio5 I did more testing:
After running the Onboarding again, there is no error in the output, the aforementioned idf paths are the same and build is still broken for me no matter how many times I restart the VS Code.
I've tried #95, but I get the exact same error. |
Excuse no response. I have been busy last days.
As I wrote before, everytime I restarted vscode, build worked again, but If I opened GUI tool, build fialed until new restart. Now, I have another issue, I think is related with this. This weekend I had to clean and format my Windows PC. After fresh OS, IDF tools and vscode + idf plugin installation, I'm facing new problem. Before 0.21 installation, onboarding configuration success, I can't start GUI tool when build folder is present. I open project and click on GUI tool button and this error is shown:
However, if I delete build folder, restart vscode and click again on GUI button, no error is shown and GUI tool opens and works great. Now, I click on build button. Build process complete succesfully and I can flash without issue. Restart again vscode, click on GUI tool button to change any parameter and same error again appears, so GUI tool doesn't work again. I can check that everytime I delete build folder, GUI tool starts and works, but when I build project, it crash again and again. I have downgraded to 0.20 version and everything works perfectly. Any error is shown. How can I check #95? Compiling from source? |
ok.. i just did a pull of #95 this should be a link to a visx with pr#95 in it https://github.com/espressif/vscode-esp-idf-extension/suites/667103160/artifacts/5951621 |
while on a path topic i was just looking at settings... and see {"IDF_CCACHE_ENABLE":"1","OPENOCD_SCRIPTS":"C:\Users\mitchjs\.espressif\tools\openocd-esp32\v0.10.0-esp32-20190313/openocd-esp32/share/openocd/scripts"} there is a mix of path delimiters \ and / (in the json is quadruple \ \ \ ) |
The reason for this is that OPENOCD_SCRIPTS is generated using
|
Please try the latest commit @mvacha It seems to be working for @mitchjs . You can clone this repository, pick branch of #95 and follow the steps in https://github.com/espressif/vscode-esp-idf-extension#build-from-source-code @jmpmscorp |
@brianignacio5 I've just tried it and it fixes the issue for me :) Thx for fixing it. |
@brianignacio5 I have tried #95 too. It seems to work. However, I have noticed strange behaviour. Starting with a fresh project (without build folder):
So, I have noticed that in order to use GUI tools without problems, you need to build firmware previously. Everytime I delete build folder and follow process 1, GUI and build works. On the other hand, process 2 always failed. |
explain what to do for the fails, and ill try to reproduce on my system |
Please, create new project, so no build folder exist, and follow point 2. Open GUI tools -> Build project -> Restart VSCode -> Open GUI tools -> Build project. Following this process and after vscode restart, when I try to open GUI tools I received this error in console:
But If process is (from fresh project or deleted build folder): Build project -> Open GUI ->Restart vscode ->Open GUI -> Build project, any error is shown and everything work as expected. |
@jmpmscorp it seems that when you start the guiconfig the value in Did you configure your extension using the command |
@brianignacio5 I'm becoming crazy with GUI and 0.21 xD. I can't figure out how to resolve it. I have completed onboarding configuration around 20 times, checking paths but I can't find where the problem is. If I downgrade to 0.20 everything works perfectly. I attach many screenshots I have done. Feel free to delete if there are too many pictures. vscode esp-idf settings where I have found "python related config": |
@jmpmscorp did you use v0.2.1 and merged with #95? |
OMG... I finally have it... Thanks @mitchjs. I was compiled and installed master branch, I think, without #95. I have downloaded directly @brianignacio5 bugfix/env-path branch. After compile it, packaged in vsix and installed, now, I haven't any problem with build and GUI. Thank you both to help me, :) |
@jmpmscorp... woohoo! |
Sorry about this @jmpmscorp Will merge to master soon. We always trying to improve the extension, we are working on adding cool features like gcov coverage, ESP-IDF rainmaker integration, heap tracing and more ! |
Describe the bug
Build randomly fails with error: "Make sure you have the build tools installed and set in $PATH".
After a restart it usually works, but not always. When it fails, there is no message in "ESP-IDF Build" output. The behavior is the same whether esp-idf is installed using the Windows installer or the wizard in the extension.
Downgrading the extension to 0.2.0 solves the problem.
To Reproduce
Expected behavior
Project gets build as ESP-IDF is installed and the extension is correctly configured.
Environment (please complete the following information):
Logs
The text was updated successfully, but these errors were encountered: