-
Notifications
You must be signed in to change notification settings - Fork 320
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 tool installation fails due to ERROR: MSys/Minggw is not supported (VSC-1020) #856
Comments
Sorry if i sound a bit emotional. To add: |
I had some stale path variables in my vscode extension settings and i probably provided wrong IDF_PATH and IDF_TOOLS_PATH |
same error |
same error installing on Windows |
This error is triggered in ESP-IDF idf.py here: https://github.com/espressif/esp-idf/blob/master/tools/idf_tools.py#L3240 It seems there is an environment variable MSYSTEM in your setup that is being detected as MSys/Mingw |
Uninstall MSYS2 and restart your computer. This env variable is set under |
On Windows, setting the VSCode default terminal profile to anything other than
|
OS
Windows
Operating System version
Windows 10
Visual Studio Code version
1.74.1
ESP-IDF version
5.0
Python version
3.10.9
Doctor command output
Don't know, nothing happens when I run this command
Extension
esp_idf_vsc_ext.log
Description
ESP-IDF tool installation fails with, because I guess it finds MinGW64 through my git bash, which is not supported?
This is my Nth attempt at installing this stuff. Before I had MSYS installed, I was able to successfully configure/install everything, but when I tried to build my project, I got the same error.
Potentially something is wrong with my environment variable setup / I need msys after all? But in the readme for this extension, msys is not listed in the pre-requisites for Windows, I feel like you could at least provide some references to IDF documentation for those, who have no experience with this whole infrastructure.
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: