Releases: bmd-studio/stm32-for-vscode
Releases · bmd-studio/stm32-for-vscode
V3.2.9
[3.2.9] - 2024-12-24
Added
- Issue #206: Did not build anything else than elf files due to the all recipe not being correct.
- Issue #212: On Windows threw an error because the build folder was already there. Now checks before using the md command. Thanks to: qwertym88
- Issue #209: Added an option to set the amount of concurrent jobs while running make
- Issue #165: Added Build and flash release option to the context menu and as a command
Fixed
- Reverted to single name build instead of a file tree based build output. Should resolve issues: #206, #205
- Linkerscript now uses a file for the objects it needs to link to prevent Windows based command line length issues. Fixes issues #210, #149, #95
- Issue #217 when using a number as the target it is converted to a number in the yaml spec. Now convert it to a string to prevent this.
- Issue #162: Powershell paths with spaces in them were not escaped properly.
- Isse #216. The nodejs download should now succeed again on windows.
v3.2.9-beta
Patch release for V3.2.8
- Add support for unit testing.
- Create a way to embed these types of projects into a CI/CD environment
- Full support for CubeIDE imports.
- Add option to select installation location for the tooling.
v3.2.8
v3.2.7-beta
Added
- Issue #84 Add -fno-rtti and -fno-exceptions as default for C++ builds.
- Added an .stm32env file which set-up the paths to openocd and the ARM toolchain. This can also be used to change other things in the build in a local setup.
- Issue #144 Added a way to change the build folder using the .stm32env file.
Fix
- Issue #181 added a way to extract the asmm part of files from the ST Makefile.
- Issue #179 now create a prompt to save cortex debug info to the global space, so is should not create a local workspace setting each time.
- Issue #176 Added a project name field for the blank setup wizard so the project has a default name.
V3.2.6
V3.3.0 beta
New release of the beta with a large overhaul of the build system.
Added
- Out of source build where it keeps the current folder structure
- Release and debug builds
- Issue #157 Use .env files to set the build tooling and other variables
- Issue #144: Be able to change the output/build directory
Fixed
- Previous release had an issue where header files were improperly included
v3.2.6 beta
Beta version for a release that has been in the works for some time. The goal of this release is to add better support for building in CI/CD pipelines using the STM32Make.mk output of the STM32 for VSCode extension.
Some note-able features:
- Debug and release builds
- .stm32env dotfile which includes user depended build tooling e.g. gcc, openocd.
- build output copies file structure in the project
- build directory can be changed by setting BUILD_DIRECTORY in the .stm32env file.
Release can be installed manually by pressing CMD/CTRL+shift+p and selecting or searching for Extensions: Install from VSIX. The included vsix file can then be installed.
V3.2.5
V3.2.4
Fixed
- Issue #139: Fixed issue where after generation something went wrong with getting new information from the makefile.
- Better SVD file finding using Levenstein distance.
- Issue #147: Fixed issue where build tools were not installing due to pre-installed node.
Added
- Issue #143: Added support for capitalized assembly file extensions (.S) as it is required for AzureRTOS.
V3.2.3
Addded
- Issue #101 & #119: Added make flags to the configuration file. This allows to add the --silent flag to the build and to prevent output mixing on parallel compilation.
Fixed
- Issue #116: Fixed issue where the STM32 configuration file would silently delete if there was something wrong while parsing the yaml file.
- c_cpp_properties.json would have reflect the current configuration. Changed it so it is regenerated upon each new build.
- Issues #125: Issue with the openocd configuration for the STM32l0 line. With thanks to: signorettae.
- Issue #91: LIBS variabel in the cube generated makefile was not read correctly.