Maxim, STM32 makefiles overwrite VS Code configuration files

[trupples]

Behaviour

The $(PROJECT_TARGET)_configure targets in tools/scripts/stm32.mk and tools/scripts/maxim.mk use the GNU Make file function to set up a default VS Code configuration for projects, with no regard to the contents of those files.

no-OS/tools/scripts/maxim.mk

Lines 139 to 143 in 3cb5f58

	$(PROJECT_TARGET)_configure:
	$(file > $(CPP_PROP_JSON),$(CPP_FINAL_CONTENT))
	$(file > $(SETTINGSJSON),$(VSC_SET_CONTENT))
	$(file > $(LAUNCHJSON),$(VSC_LAUNCH_CONTENT))
	$(file > $(TASKSJSON),$(VSC_TASKS_CONTENT))

For context, the content of the files is generated in vsc_intellisense.mk, vsc_openocd_debug.mk, and vsc_tasks.mk.

Impact

With the current makefiles, one may not change their VS Code config without it being reset to the no-OS defaults during the next build, which greatly hinders development. For instance, my WSL dev setup requires changing the gdb options in launch.json, but doing so is futile because the makefile resets my changes when building.

Options

I suggest (and will shortly open a PR) adding a condition to only write to these files if they are empty or don't exist (i.e., during project setup), but keep their current content otherwise, to allow for customization of the config.

Despite some effort, I didn't manage to do it using just GNU Make syntax, but rather by changing the file call from filename.json to filename.json.default, and having some shell commands conditionally copy filename.json.default to filename.json if the latter doesn't exist. Finally, shell commands remove the .default files to keep the directory tidy.

[CiprianRegus]

The commits were merged.