-
Notifications
You must be signed in to change notification settings - Fork 315
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
Unable to resolve configuration with compilerPath (VSC-1248) #1083
Comments
Change |
Thank you, it helped. |
I tried installing the esp-id on another computer and there I had another problem with this line. When creating a project (clean or from an example), the problem line looks like this: I do not know if I should create a new issue to solve this problem, so I wrote here |
I'll make a bug fix for this a new PR.
Seems your extension might not be configured since the last part is giving undefined. Will check out too so it doesn't use this value. |
It could be settings sync. I would recommend to disable if settings across machines have different locations. |
I have same issue, where I can change this settings please ? |
.vscode/c_cpp_properties.json in your project |
This issue has been marked as |
This issue has been marked as |
Im getting the same error "compilerPath": "${config:idf.toolsPathWin}undefined", |
This might be related to your extension not being configured properly at the time you created the project. Check the |
OS
Windows
Operating System version
Windows 11
Visual Studio Code version
1.84.2
ESP-IDF version
5.1.2
Python version
IDK, installed via ESP-IDF Setup
Doctor command output
Extension
I couldn't insert the log because "Comment is too long (maximum is 65536 characters)"
Description
The project is building normally, but when running vs code, C/C++ issues a message
Is this normal behavior? I would like to remove these messages because they are very annoying.
Debug Message
Other Steps to Reproduce
I deleted the ESP-IDF extension and its folders because I installed it a long time ago. Then I installed the extension again
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: