Hello,
We had installed STM32CubeIDE 1.13.0 on a network drive (V: drive is the mapping), and it worked nicely to build a project cloned from git repo on the local drive (C:).
With STM32CubeIDE 1.17.0 and 1.18.0, the IDE fails to build. Even cleaning and re-building dos not make the build succeed. If however the STM32CubeIDE is launched from C: drive, it is able to build the project.
The CDT make lists the arm-none-eabi-gcc command line with all the right arguments, and there is no attempt to even run the executable. The very next line has make reporting failure in the very first build in a subdir.mk file, and make terminates with exit code 2.
This does not happen if using STM32CubeIDE 1.13.0 from the same network drive.
