Microsoft C/C++ Extension dropped support for non-oficial vscode forks

With the latest change, Microsoft removed the ability to run their C/C++ extension from any non-oficial VSCode fork, including non-profit ones like VSCodium.

Are there any plans (besides reverting the extension to previous one) to mitigate this? Or will PlatformIO IDE be VSCode exclusive in the near future?

Maybe going clangd route?

Thanks for this awesome software!

Best discussed with the maintainers of the IDE extensions. For which there already is an issue:

CC @ivankravets

1 Like

We are always eager to provide true freedom to PlatformIO users. However, our mission does not always align with that of other businesses. Microsoft is a profit-driven company that has never truly prioritized the needs of developers - they simply follow their business interests.

We have an open ticket regarding this issue. At the moment, there is no working solution that can compete with what Microsoft has created. See:

vscode.cpptools v1.24.4 is the last one NOT having base tool check

There’s a related issue that suggests the need for a different C/C++ extension, at least in some cases: The official extension doesn’t support any non-standard keywords (such as type qualifiers like __xdata used by sdcc to specify address space) and the issue has been considered too lacking in demand to implement some sort of grammar-injection solution. At least if there is I can’t figure it out.

Just in case it is of any use, I was looking at the EmbeddedIDE extension to see what it was doing. I haven’t followed all the code yet, but it looks like they are registering a ConfigurationProvider for both cppTools and clangd:

(Of course I don’t like their extension as much as PlatformIO, though it hasn’t been around as long so not surprising if it isn’t as refined overall.)