Currently, STM32Cube for Visual Studio Code introduces a new bundled package manager which replaces STM32CubeCLT.
However, when developing STM32 projects with other IDEs (e.g. CLion), STM32CubeCLT is still required to provide the build environment.
This leads to several problems when using multiple IDEs (VS Code + CLion):
Separate installations of toolchains (STM32Cube for VS Code and STM32CubeCLT) consume extra disk space.
STM32CubeCLT cannot be updated incrementally; users must download the whole package.
STM32Cube for VS Code currently cannot manage STM32CubeCLT packages, leading to duplicated toolchain management.
By default, tools are installed on C:\ drive, which is inconvenient for users with limited system disk space.
Feature request:
Benefits:
Reduce disk usage by avoiding duplicated toolchains.
Simplify updates and package management.
Improve developer experience when using multiple IDEs (VS Code + CLion, etc.).
