Issue with "--multi-lib-config" error when using ST-ARM-CLANG in VS Code

[amazone]

hi dear,

I created a project by selecting CMake as the toolchain and ST-ARM-CLANG as the compiler using the STM32Cube extension for VS Code (3.7.0) on macOS. Attached below are my configuration settings.

 

  

 

The project builds successfully without any issues in the terminal. However, I am seeing the following error in the VS Code editor:

"error: unknown argument: '--multi-lib-config=...'"

"message": "Unknown argument: '--multi-lib-config=/Users/myName/Library/Application Support/stm32cube/bundles/st-arm-clang-hybrid-19_1_6-description/0.0.6+st.1/etc/multilib.gnu_tools_for_stm32.yaml'",

clang(drv_unknown_argument)

 

Please let me know if there`s a solution for this. Thanks!

 

Also, I would like to know how to enable float support for printf() in the CMake-based ST-ARM-CLANG environment.

 

 

[Julien D]

Hi @amazone,

I've just tried using STM32CubeMX 6.15 to generate a project for my F446RE-Nucleo board, and I was able to open it in VSCode and build it on MacOS.

Maybe you missed doing the project setup?

If so you can force it manually via the Setup STM32Cube Project action.

 

[amazone]

Hi, @Julien D 

I set up the same STM32CubeMX 6.16.1 project for the F446RE-Nucleo board. I've finished the setup in VS Code as you described.

In starm-clang.cmake, STARM_TOOLCHAIN_CONFIG is set to STARM_PICOLIBC by default. Under this setting, the build completes successfully when main.c is open. However, if I change STARM_TOOLCHAIN_CONFIG to STARM_HYBRID and attempt to build with main.c open, an error occurs.

 

[Julien D]

I managed to reproduce what you observed on my side as well.

 

It is not an issue related to your project configuration; it is a known bug in the ST extensions that affects clangd, the indexing service for CLANG projects.

That being said, for now, you can ignore this type of error message in the problem view and editor while waiting for a fix, which should be released in 2026.

[Julien D]

Hi @amazone,

FYI a new release of the extensions containing a fix for this issue has just been published.