2025-10-20 4:00 PM - edited 2025-10-20 4:00 PM
For quite some time now, both with the STM32CubeIDE and now with this VSCode extension, empty projects lack the device specific header files that will be needed to work with the selected device. Usually, the way I have done it in the past is that I navigate to the STM32Cube repository folder to copy about six header files and the system source file to my project directory. It is cumbersome.
I believe I have made a post regarding this before back in 2020, Why does creating an empty project not add header files
Some workarounds were to create a Cube project and then delete the .ioc and HAL files as well as removing the compiler defined symbols that specify to use the HAL driver. This works and I have been using this method. However, it is a bit cumbersome, and I think that if the empty project already contain bare-bones files for the selected device, it should also include the necessary device specific files as well to save some of the burden of locating the relevant files and copying them across
Thanks
2025-10-20 10:45 PM
@Adam Hamilton, thank you for sharing your feedback again. We truly appreciate and welcome input that helps us prioritize our roadmap.
Please see https://community.st.com/t5/stm32cubeide-for-visual-studio/quot-create-empty-project-quot-does-not-provide-cmsis-files/td-p/819374 and feel free to add your comments.