Can prepend PATH in kit?

I have two mingw : C:\mingw32 and C:\mingw64 so not good to add both to PATH. Add below to cmake-kits.json but not work:

	{
		"name": "mingw64",
		"compilers": {
			"CC": "c:/mingw64/bin/gcc.exe",
			"CXX": "c:/mingw64/bin/g++.exe"
		},
		"environmentVariables": {
			"PATH":"C:\\mingw64\\bin;${env:PATH}"
		}
	}

[vector-of-bool]

Looks like a separate prependPath and/or appendPath option to kits might be of good use…

[andreeis]

@pm-energid, yes we should explain environmentSetupScript. Our documentation needs some updates in general.

Regarding execution of a script before any call to cmake. Does it really have to be every time before any cmake invocation (configure, build, …etc) or once at load time is enough, as long as the environment changes are persisted throughout the entire VSCode session? environmentSetupScript is meant to keep the environment effects of running it for all the future configure/build operations during the current VSCode session. Let us know if that’s not the case (it would be a bug that we’d want to fix).

I am glad that trying the latest vsix confirmed that the environment settings expansion bug was fixed. So, are you completely unblocked and your scenario works or there’s something else you’d like us to address?