2025-07-13 1:09 PM
I am using the STM32Cube VS Code extension (Preview) with the official ST-ARM-CLANG and clangd for code completion. Just ran into two issues:
1. Incomplete --query-driver config breaks C++ IntelliSense
The extension adds
--query-driver=${env:CUBE_BUNDLE_PATH}/st-arm-clang/19.1.6+st.8/bin/starm-clang.exe
to settings.json by default, but this is not enough for C++ files.
Unless you also add
--query-driver=${env:CUBE_BUNDLE_PATH}/st-arm-clang/19.1.6+st.8/bin/starm-clang++.exe
C++ IntelliSense will be broken (red squiggles, no symbols, etc).
Same issue for GCC toolchain: you need both gcc and g++ in the driver list.
2. --multi-lib-config triggers errors in clangd
If you enable --multi-lib-config, clangd just starts throwing errors about missing headers and stuff, even though the project still compiles fine.
Is this a known issue? Anyone have a workaround?
By the way, is there any official way to download the standalone ST Arm Clang toolchain (without the VSCode extension)?
It would be super useful for CI/CD or automation, similar to how STM32CubeCLT was distributed before.
Thanks!