RE: NCS Getting Started Assistant Install using Toolchain Manager Tools

Didrik Rokhaug — Wed, 24 Feb 2021 10:26:32 GMT

After discussing this issue with our developers, we have found the issue.

To make it easier to use the toolchain from the Toolchain Manager (TM), the installed toolchain gets registered in the CMake package registry.

This will allow you to use the Segger Embedded Studio Nordic Edition (SES-NE) without opening it from the TM, but instead by e.g. pinning it to the taskbar.

When using SES-NE, you can select the right toolchain when you open a new NCS project.

If you are using West, you can select the toolchain version by adding an argument to CMake, e.g. west build ... -- -DNCS_TOOLCHAIN_VERSION=1.5.0. You can also set the toolchain version to NONE, if you want to use manually-installed tools.

If there is a compatible NCS toolchain, the default behavior is that West will use that, rather than manually installed tools.

This normally works without issues, but with NCS 1.5.0, the requirements to the toolchain has changed. However, the minimum required NCS toolchain version was not updated in the build system. This caused West to believe that an incompatible toolchain would work, which is what caused the error.

The toolchain requirement has now been updated (PR #4002), but it is not part of the rc1 tag. You should therefore not encounter this build problem when the 1.5.0 release is done.

There is currently no simple way of changing this default behavior, but we are looking into ways of improving it.

Currenty. the workarounds are to uninstall the NCS toolchains, or rename the folders.

RE: NCS Getting Started Assistant Install using Toolchain Manager Tools

Didrik Rokhaug — Tue, 23 Feb 2021 15:17:50 GMT

Hi,

We have recently noticed this behavior, and we are looking into the causes.

Removing the Toolchain Manager installations seems to work as a workaround, though it isn't ideal.

I will let you know as soon as I know more.

Best regards,

Didrik