In ticket Case ID 290251, Torsten Rasmussen provides the following advice to ensure that the toolchain corresponding to the SDK is used to build the SDK (this applies to nrfutil and nRF Connect for Desktop's Toolchain Manager)
To avoid typing this for each build in this workspace, you can set this permanently for the workspace using `west config` like this:
west config --local build.cmake-args -- -DNCS_TOOLCHAIN_VERSION=2.0.0
(The advice was provided for working with v2.0.0 SDK of course.)
My question is why is this not set up for us in <SDK TREETOP>/.west/config when we download a version of the SDK.
The current situation is thatunless you use VS Code you build with a somewhat random toolchain (or even pair of toolchains)
unless you have done an enormous amount of research to know that NCS_TOOLCHAIN_VERSION needs to be set (either to NONE or the SDK version you are building in).
The chances of having the build system try to pull the python executable and the rest of
python from two different toolchains and then failing is pretty large for most users that are not familiar with the NCS_TOOLCHAIN_VERSION define.
Thanks,
Burt Silverman