Feature Request: Support for Customizable Generated Code Directory Structure in STM32CubeMX
Dear STM32 Team,
In large-scale embedded projects that span multiple hardware platforms and coexist with multiple application firmware instances, the current STM32CubeMX workflow creates a full independent copy of HAL/LL libraries for every single project workspace. This redundant duplication makes it extremely difficult to maintain a unified, shared library baseline across the entire codebase.
At present, I have to manually copy the auto-generated src/ and inc/ files from CubeMX output into our standardized fixed project directory structure. This manual workaround completely breaks the native iterative maintenance flow: every subsequent re-generation of code via CubeMX requires tedious manual file migration, which introduces high risk of configuration mismatch and human error.
It would be a highly valuable feature if STM32CubeMX could add a dedicated configuration panel to let users fully define the custom directory hierarchy for all generated source files, header files, and library components, rather than enforcing the fixed default output structure. This will drastically improve the development experience for complex multi-project, multi-platform embedded systems.
Thank you for considering this practical optimization for professional development scenarios.