toolchain installation directory relative to VSCode workspaceFolder?

[C.Thilo]

HI!

We want to use different toolchains folder per VSCode projects, but it seems, that the nrf-connect setting "nrf-connect.toolchainManager.installDirectory" is not capable of working with ${workspaceFolder} Variable nor with a pur relative path like "..".

On the other hand, it seems, that it must point to a folder where a folder "toolchains" exists in, in which a toolchains.json file lives. ....
Is this correct? IMHO, it would be more nice to just point to a folder, where the toolchains.json is and not to a hardcoded toolchains folder.

Anyway, it would be nice if there is more docu to the installDirectory setting and how to setup custom folder installation with this setting.

Is it anyhow possible, to use not absolute paths with this setting?

Cheers
Thilo

[C.Thilo]

Nope ... it was just me :).

Setting the installDirectory in the code-workspace under "settings": does the trick!

{
	"settings": {
		"nrf-connect.toolchainManager.installDirectory": "${workspaceFolder}/.."
	}
}

But still it needs to point to a folder, where a folder "toolchains" exists, inside which the toolchains.json resides.

[C.Thilo]

But now, when I build via nrf-connect for VS Code, it will not recognize the build configuration after a successful build.
Under Build and Actions the "Pristine Build" button appears after each build, although, the build worked as it should.

In the nrf Connect output I can find:

[08:36:37] west build --build-dir ..../build ..... --pristine --board .... -- -DNCS_TOOLCHAIN_VERSION=NONE -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y
[08:36:56] Success.

But it still shows: