Skip to content
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

[Feature Request]: Add linker (ld) failures to VS Code 'Problems' window (VSC-1492) #1315

Open
GillesZunino opened this issue Sep 18, 2024 · 0 comments · May be fixed by #1317
Open

[Feature Request]: Add linker (ld) failures to VS Code 'Problems' window (VSC-1492) #1315

GillesZunino opened this issue Sep 18, 2024 · 0 comments · May be fixed by #1317
Labels
Feature / Enhancement Request Request for Feature/ Enhancement

Comments

@GillesZunino
Copy link

When building a project in VS Code ESP IDF Extension (v 1.8.1), any linker error is reported in the terminal. These errors are not reported in the 'Problems' list of VS Code. Users have to sift through the build log and extract linker errors. This can also confuse new users as ESP IDF will say "build failed" and the problems list will be empty.

In an ideal world, ld errors would be reported in the problems list, possibly as follows:
image

Notice the file name being reported as well as the line number so the entry is clickable and will open the file which references the missing linker item

@GillesZunino GillesZunino added the Feature / Enhancement Request Request for Feature/ Enhancement label Sep 18, 2024
@github-actions github-actions bot changed the title [Feature Request]: Add linker (ld) failures to VS Code 'Problems' window [Feature Request]: Add linker (ld) failures to VS Code 'Problems' window (VSC-1492) Sep 18, 2024
@GillesZunino GillesZunino linked a pull request Sep 24, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature / Enhancement Request Request for Feature/ Enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant