Hey, For some reason I don't get compile warnings or errors listed in the VSCode problems tab. Any ideas why? See video below for a demo.
Hey, For some reason I don't get compile warnings or errors listed in the VSCode problems tab. Any ideas why? See video below for a demo.
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...
I don't think this was ever removed. What missing errors do you refer to?
What I see is that the Kconfig warnings in the problems tab, for example if I set:
Is that not present in your case?
Yes, only Kconfig warnings show, but not build warnings / errors of actual C/C++ code...
So you wouldn't see this?
BR,
Edvin
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...
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
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
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
.
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
Great, thank you for your attention on this! :)