0xemgy

I tinkered with the gcc parser because showing the linker errors in the Problems panel is really helpful. What I basically did is I added some more regex cases and...

> @0xemgy Thanks for the investigation and comments. > > This seems like a GREAT opportunity for you to improve the extension for everyone by making an Open Source Contribution!...

@gcampbell-msft @v-frankwang I was able to test my solution throughout the last months (using it almost every day at work). Regarding my previous concerns: 1. I left the pending error...

@gcampbell-msft @v-frankwang I think I got it: Forked the repo, created a PR, agreed to the CLA: https://github.com/microsoft/vscode-cmake-tools/pull/3950

@gcampbell-msft @v-frankwang It turns out there already is a GNU linker error parser in your code base. The CI unit test in my PR [#3950](https://github.com/microsoft/vscode-cmake-tools/pull/3950) failed because the unit test...

@RolfNoot I created a new branch in my forked repo, see branch `dev/0xemgy/FixGnuLdProblemsViewPrompt` [here](https://github.com/0xemgy/vscode-cmake-tools/tree/dev/0xemgy/FixGnuLdProblemsViewPrompt), with the solution I'm confident @gcampbell-msft will prefer (keeping the gnu ld parser). I generated a...