Skip to main content
TDJ
Senior III
July 25, 2026
Question

Getting started with STM32CubeIDE for VS Code (rev 3.10)

  • July 25, 2026
  • 4 replies
  • 66 views

Hi ST,

Today I decided to give STM32CubeIDE for VS Code another try.

I installed all 15 latest packages (Rev. 3.10).
Using the STM32Cube Bundle Manager, I installed all required bundles, including Ninja 1.13.2.

After opening in VS Code the folder containing the code generated by STM32CubeMX (CMake option) and trying to configure CMake for the first time (Ctrl+Shift+PCMake: Configure), I received the error below.

What am I missing? The last time I tried this several months ago, the project at least configured correctly and built successfully.

 

Kind regards,

Thomas

 

[main] Configuring project: Firmware

[driver] NOTE: You are configuring with preset Debug, but there are some overrides being applied from your VS Code settings.

[proc] Executing command: "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=C:/Projects/All-purpose-Micro-Controller-2/Firmware/cmake/gcc-arm-none-eabi.cmake -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -S C:/Projects/All-purpose-Micro-Controller-2/Firmware -B C:/Projects/All-purpose-Micro-Controller-2/Firmware/build/Debug -G Ninja

[cmake] CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

[cmake] -- Configuring incomplete, errors occurred!

[proc] The command: "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=C:/Projects/All-purpose-Micro-Controller-2/Firmware/cmake/gcc-arm-none-eabi.cmake -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -S C:/Projects/All-purpose-Micro-Controller-2/Firmware -B C:/Projects/All-purpose-Micro-Controller-2/Firmware/build/Debug -G Ninja exited with code: 1

 

4 replies

Cartu38 OpenDev
Graduate II
July 25, 2026

@TDJ 

Sounds weird you had to install bundles by yourself. Installing extensions is leading to a notification in the right bottom corner to manage this.

Same sounds you have missed a notification then adding your project to workspace. You have to accept enriching it as a STM32Cube project. This process setup it right enabling proper tooling to edit build and debug.

You can this process explicitly thanks dedicated key action so called "Setup project"

Cartu38 OpenDev
Graduate II
July 25, 2026

@TDJ 

See 

 

TDJ
TDJAuthor
Senior III
July 25, 2026

@Cartu38 OpenDev 

Thank you. I believe I am following the correct procedure, but it still does not work. Ninja is missing :(
See here:

 

Cartu38 OpenDev
Graduate II
July 26, 2026

@TDJ 
Thanks for sharing video. Unfortunately lacking THE key step about folder addition to VS Code workspace.
Looking at yoiur explorer view I can confirm project setup is not completed to no say not executed at all. All your pain is due to.

Your project is going to be a STM32Cube project - having so all proper tooling like cmake and ninja set - if .settings folder is created at your folder root. Here I can see .vscode but that’s all and it’s not enough. .settings folder has to host x3 files at the end.

I suggest back to invoke project setup
 

or to remove your folder from workspace and add it back taking care about the magic notifcation then