VSCode Compiler errors & Warnings do not appear in VSCode problems tab

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Thu, 15 Feb 2024 10:27:05 GMT

Great, thank you for your attention on this! :)

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Thu, 15 Feb 2024 09:00:23 GMT

Thank you! I have posted this as a feature request to the team developing our VS Code extensions, together with a summary of what we have discussed.

Best regards,

Edvin

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Wed, 14 Feb 2024 15:12:54 GMT

Here is a simple example, two projects, each have "unused variable" warnings. For Espressif, you see if shows in the problems tab, for the NCS SDK, which I'm using the latest of everything, it does not show in the problems tab

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Wed, 14 Feb 2024 14:59:23 GMT

I understand.

Obviously, it is probably difficult for you to show what the build errors used to look like, if you are not seeing them anymore. Do you see them if you roll back to an earlier version of nRF Connect for VS Code?

If not, perhaps you can show an example of what it looks like from one of the other MCUs?

Best regards,

Edvin

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Wed, 14 Feb 2024 13:43:58 GMT

That's not a build issue of errors reported from the nRF SDK, that's a C/C++ issue as reported from the Microsoft C/C++ extension. So there is a difference in warnings / errors with the nRF sdk vs a C/C++ warning / error. All other MCU's have warnings / errors reported, i.e. Espressif, Silicon Labs, etc... Nordic does not...

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Wed, 14 Feb 2024 13:40:34 GMT

So you wouldn't see this?

BR,
Edvin

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Wed, 14 Feb 2024 10:19:59 GMT

Yes, only Kconfig warnings show, but not build warnings / errors of actual C/C++ code...

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Wed, 14 Feb 2024 10:18:08 GMT

What I see is that the Kconfig warnings in the problems tab, for example if I set:

Is that not present in your case?

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

jonas.woerner — Tue, 13 Feb 2024 11:21:36 GMT

yes, I also think its a huge inconvenience. its really bad to always have to search the build output if it could be so so so much better.

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

robsrick — Mon, 12 Feb 2024 13:03:39 GMT

+ This definitely used to work and some release of the nrf tooling broke it - whether or not it was intended as a feature.

... but it's hard to understand how this isn't an intentional feature when every other compiler integration with VSCode uses the problemMatchers. Pretty basic feature.

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Mon, 12 Feb 2024 10:47:29 GMT

Hmmm... strange, as others have posted, these warnings / errors had shown in the problems tab before, so this must be a new change / stance on the state of the plugin. Huge inconvenience, so it would be nice to have this added as a feature request as soon as possible...

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Mon, 12 Feb 2024 07:47:01 GMT

Oh, Sorry. I misunderstood. Yes. The build errors have never been part of the problems tab, no. And as far as I know, it is not planned to be. I can add it as a feature request. However, for now you must use the build output.

Best regards,

Edvin

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Fri, 09 Feb 2024 14:14:54 GMT

The problem is exactly as the original posting states, nothing has changed, errors / warnings still do not appear in the "problems" tab...

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Fri, 09 Feb 2024 14:12:44 GMT

I don't think this was ever removed. What missing errors do you refer to?

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Application Ninja — Thu, 08 Feb 2024 14:32:47 GMT

We need this feature added back in, any further status on this? Why were warnings / errors removed? We need the option to turn on/off at will, please advise...

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

jonas.woerner — Thu, 30 Mar 2023 13:39:58 GMT

I also would love to have the problems tab work, or at least some error highlighting (red=error, yellow=warning) in the terminal output. where is that task.json? I cant find one on my system.

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

robsrick — Mon, 13 Mar 2023 10:36:36 GMT

No worries about the build errors. I've solved those it was just a general question on how to utilise the vscode problem matcher.

It turns out, by setting "$gcc" to the top entry in the ProblemMatcher array for each build in task.json it will direct the build errors and warnings to the problems tab on vscode. I read a post last week that suggested the feature had been removed around 5-6 months ago due to a clash with intellisense? not really sure why though it seems to add a lot of value having it enabled.

Task.json

{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "nrf-connect-build",
			"config": "c:\\dev\\nrf\\neptune\\build",
			"runCmake": false,
			"clean": true,
			"problemMatcher": [
				"$gcc",
				"$cmake",
				"$kconfig",
				"$kconfig_syntax",
				"$kconfig_syntax_files",
				"$dts",
				"$dts_syntax",
			],
			"group": "build",
			"label": "nRF Connect: Build [clean]: neptune/build (active)"
		},
		{
			"type": "nrf-connect-build",
			"config": "c:\\dev\\nrf\\neptune\\build",
			"runCmake": true,
			"clean": false,
			"problemMatcher": [
				"$gcc",
				"$cmake",
				"$kconfig",
				"$kconfig_syntax",
				"$kconfig_syntax_files",
				"$dts",
				"$dts_syntax",
			],
			"group": "build",
			"label": "nRF Connect: Build [pristine]: neptune/build (active)"
		},
		{
			"type": "nrf-connect-build",
			"config": "c:\\dev\\nrf\\neptune\\build",
			"runCmake": false,
			"clean": false,
			"problemMatcher": [
				"$gcc",
				"$cmake",
				"$kconfig",
				"$kconfig_syntax",
				"$kconfig_syntax_files",
				"$dts",
				"$dts_syntax",
			],
			"group": "build",
			"label": "nRF Connect: Build: neptune/build (active)"
		}
	]
}

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Edvin — Mon, 13 Mar 2023 10:25:10 GMT

Marte is out of office, so I will handle this ticket.

As far as I know, there are no plan to change where the compile errors are printed.

As for the compiler errors themselves, I was not able to see the build log from your video. Please copy the output from the build, and paste it here using Insert -> Code, as Marte said.

Best regards,

Edvin

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

robsrick — Tue, 07 Mar 2023 12:47:06 GMT

Oh right, I'm sure I saw it happen sporadically in the past. Is there a plan to add this? It would be very nice to have the formatted error / warnings in the standard VSCode way.

RE: VSCode Compiler errors & Warnings do not appear in VSCode problems tab

Marte Myrvold — Tue, 07 Mar 2023 12:35:26 GMT

Hi,

Build errors and errors from the nRF Connect for VS Code extension do not appear in the problems tab. You must look at the terminal output. If you need help solving the errors you are getting, please copy and upload the entire build log here using Insert > Code.

Best regards,

Marte