jortbmd
commented
1 year ago Hi! Thanks for opening up an issue for this. It is possible that the character limit is reached I have encountered this before on Windows and there is a feature in the works for this, which allows you to select an installation location for the tools. For now the quickest thing to do would probably be to go to copy all the tooling in your: "c:/users/user/appdata/roaming/code/user/globalstorage/bmd.stm32-for-vscode/@xpack-dev-tools" folder and change your settings for the build tools paths for STM32 for VSCode. Let me know if this helps.
I will also update you once the new feature is implemented.
Hi, I am getting this error when trying to build my project
arm-none-eabi-gcc: fatal error: cannot execute 'c:/users/user/appdata/roaming/code/user/globalstorage/bmd.stm32-for-vscode/@xpack-dev-tools/arm-none-eabi-gcc/11.3.1-1.1.2/.content/bin/../libexec/gcc/arm-none-eabi/11.3.1/collect2.exe': CreateProcess: No such file or directory compilation terminated. make: *** [STM32Make.make:1177: build/Heimdall.elf] Error 1
The project is pretty big, so im suspecting that the character limit for the windows terminal is being reached when linking all the object files. Am I correct, and if so how do i bypass this?