"STM32Cube for Visual Studio Code" extension pack conflicts with MS C++ (cpptools) extension

Giocc1 · ‎2025-09-04

The extension signals the conflict as in subject and suggests to disable intellisense altogether.
MS C++ (cpptools) is a very popular extension required by many others, so disabling it is not an option.
Another solution might be to disable the individual stm32-cube-clangd extension, but does it have any drawback? What's the point of having an useless and incompatible extension?

vincent_grenet · ‎2025-09-04

@Giocc1 you can disable stm32-cube-clangd extension if it's your choice. No drawback at all for now doing such.
Right now we are even helping MS C++ (cpptools) support if the one you want to elect adding some .vscode\c_cpp_properties.json.

"for now" is because we are thinking to improve indexing experience and we only can do it relying on open source assets clangd & collaterals are. MS C++ (cpptools) is private solution ... but we are aware very popular one yes.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

vincent_grenet · ‎2025-09-04

@Giocc1 you can disable stm32-cube-clangd extension if it's your choice. No drawback at all for now doing such.
Right now we are even helping MS C++ (cpptools) support if the one you want to elect adding some .vscode\c_cpp_properties.json.

"for now" is because we are thinking to improve indexing experience and we only can do it relying on open source assets clangd & collaterals are. MS C++ (cpptools) is private solution ... but we are aware very popular one yes.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.