[BUG] STM32Cube CMake Support: Infinite "Select hardware" Popup in VSCode Multi-Root Workspace

[parmi93]

The STM32Cube CMake Support extension blocks the VSCode UI when multi-root VSCode workspace are opened. Specifically, if a multi-root workspace is opened, the STM32Cube CMake Support extension continuously shows the Select hardware window. Even if the user closes the window by pressing Esc, it immediately reappears, preventing the user from doing anything, since that window has the highest priority.

This happens because the extension detects the CMakeLists.txt file in the sub-workspace another_generic_cmake_project (see attached project) and, for some reason, attempts to configure the sub-workspace as an STM32Cube project, even though it is not an STM32 project but a generic CMake project.

Currently, as a workaround, I have to add the setting:

	"settings": {
		"stm32cube-ide-build-cmake.ignoreCubeProjectDiscovery": true,
	}

to the multi_root_project.code-workspace file, which prevents the STM32Cube CMake Support extension from attempting to detect the main workspace and any sub-workspace as STM32Cube projects.

 

Attached is a small example project that reproduces the issue. Open it by double-clicking on multi_root_project.code-workspace.

[Nawres GHARBI]

Hi @parmi93 

Currently, the project structure handled by the extensions does not support projects nested within other projects.
Therefore, it is expected to encounter such issues or error messages when using this type of project organization.

In parallel, we are working on improving the project structure management in order to support these scenarios in future releases.

We will use your project as a reference case for our analysis. If you have any additional ideas, typical workflows, or alternative ways of organizing your projects, please feel free to share them with us. We will carefully review these inputs for potential inclusion in future implementations.

[parmi93]

The extension should provide an option to prevent nested projects (sub-workspaces) from being treated as STM32Cube projects.

One possible solution could be that if a nested project has the setting "stm32cube-ide-build-cmake.ignoreCubeProjectDiscovery": true in its .vscode/settings.json, then the STM32Cube CMake Support extension should not treat that nested project as an STM32Cube project.

 

Attached is a project where I added the option "stm32cube-ide-build-cmake.ignoreCubeProjectDiscovery": true in multi_root_project_with_ignoreCubeProjectDiscovery/another_generic_cmake_project/.vscode/settings.json, where ideally the STM32Cube CMake Support extension should ignore the sub-workspace and avoid treating it as an STM32Cube project.