NCS and toolchain version in CMakePresets.json

[Remo]

Hi

In the newer versions of nRF Connect for VS Code, the NCS and toolchain version can be configured per build-configuration.

Is it possible to configure the desired versions in the CMakePresets.json so that the correct version is chosen when a new build-configuration is created?

Many thanks in advance.

Best regards

Remo

[dejans]

Hi,

You can have a look at this discussion about CMakePresets.json. Please let me know if you have any further questions.

Best regards,
Dejan

[Remo]

Hi Dejan

I've read the linked discussion, but it doesn't say anything about pre-setting the versions of the NCS and the toolchain in CMakePresets.json. Have I missed something?

Best regards
Remo

[dejans]

Hi Remo,

I misread your question somehow. I am sorry for that.

Is there a reason why you want to use CMakePresets instead of west workspaces for having persistent NCS and Toolchain versions?

Can you elaborate on your desired way of using CMakePresets.json?

Best regards,
Dejan

[Remo]

Hi Dejan

No problem.

To be honest, I don't know west workspaces. We have used the CMakePresets so that every of our developers can create a build-configuration for our own target-board based on one of the presets (so that e.g. the target CPU, the Kconfig file, the overlay file and optimization-level are already defined).

Therefore, it would have been nice if also the NCS and toolchain version could have been defined CMakePresets. Is this currently not possible?

Best regards

Remo

[dejans]

Hi Remo,

Remo said:

it would have been nice if also the NCS and toolchain version could have been defined CMakePresets. Is this currently not possible?

I will check this internally. I expect to provide update by the end of this week.

Best regards,
Dejan