Upgrade CMake version of nRF Connect toolchain

RE: Upgrade CMake version of nRF Connect toolchain

Grow Garden — Fri, 24 Apr 2026 04:59:23 GMT

This is a practical workaround for upgrading CMake in nRF Connect toolchains, but a cleaner per-project configuration or toolchain override would be more stable and maintainable than modifying system directories.
grow garden

RE: Upgrade CMake version of nRF Connect toolchain

Jack Lin — Wed, 28 Aug 2024 19:42:46 GMT

Hi Priyanka, has there been any updates on this? I'm running into this issue too.

RE: Upgrade CMake version of nRF Connect toolchain

Priyanka — Tue, 20 Aug 2024 09:34:17 GMT

Hi Eric,

I am working on this and will get back to you soon. Will keep you updated.

RE: Upgrade CMake version of nRF Connect toolchain

ebariaux — Fri, 16 Aug 2024 08:18:33 GMT

Thanks for the feedback.

Using VM is a possibility (I've used some macOS VM with UTM) but it's quite heavy.

Using docker might work, but I haven't explored calling the toolchain in a docker container from VSCode running on the host.

There's only 1 symlink, I can also easily have a script to change the symlink based on the project I'm working on.

But in the end, using a symlink to change the CMake version doesn't feel right to me, so I was hoping for a cleaner solution.

RE: Upgrade CMake version of nRF Connect toolchain

Jacobjsdhfg — Mon, 12 Aug 2024 06:55:26 GMT

If you frequently switch between projects that require different CMake versions, consider using Docker or a virtual environment. This allows you to encapsulate your development environment, including the specific CMake version needed for each project.

drive mad

RE: Upgrade CMake version of nRF Connect toolchain

Priyanka — Thu, 08 Aug 2024 10:40:56 GMT

Hi Eric,

Apologies for the delay. I have consulted this internally and will get back to you.

-Priyanka