Upgrade CMake version of nRF Connect toolchain

[ebariaux]

Hello,

Is there an easy way to upgrade the CMake version that is used during the build process trigger from the nRF Connect SDK Extension in VSCode ?

I'm currently using toolchain version 2.6.0, which is using CMake version 3.21.0

I need to use at least version 3.29 (using Embedded Swift for development).

I'm working under macOS and managed to get a project working by replacing the 3.21.0 folder under /opt/nordic/ncs/toolchains/580e4ef81c/Cellar/cmake/ by a symlink to my more rect installation of CMake, so

ln -s /opt/homebrew/Cellar/cmake/3.30.1 /opt/nordic/ncs/toolchains/580e4ef81c/Cellar/cmake/3.21.0

Is there a cleaner way to do this, using some configuration ?

Above solution works but it applies to all projects and it's a hack.

Thanks,

Eric

[Jacobjsdhfg]

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

[ebariaux]

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.

[Priyanka]

Hi Eric,

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