updating the SDK to 2.8.0 resulting in non working cmake compilation.

[Eyal_Gal]

I have a sample app (hellow world from the zephyr samples).

It compiled well on my system in vscode using 2.7.0 and sysbuild.

I then installed 2.8.0 and suddenly the build fails, the cmake cannot find the python libraries.

The reason seemed to be that even though i have defined the default SDK and toolchain to be 2.7.0 when calling ncsconfig.cmake it finds toolchain for 2.8.0 and not 2.7.0

i tried to set -DNCS_TOOLCHAIN_VERSION=v2.7.0 instead of None in west call, but it did not help.

Any idea how to resolve it ?

If i remove 2.8.0 then everything goes back to normal, but i want the ability to move some of the new projects to 2.8.0 without docker.

Please advise.

[Edvin]

Hello,

I am sorry for the late reply. How did you install NCS and the toolchain? 

Is it possible to upload the application that triggers this issue, so that I may have a look, and see if I can replicate the issue or not?

Best regards,

Edvin

[Eyal_Gal]

Hi Edvin!

Please check above i have described in details how i installed things from scratch on a VM with ubuntu 22.04.5.
as for your questions:

1. i installed all toolchains and SDKs using vs code plugin.

2. i have installed 2.7.0 first and then i installed JUST the 2.8.0 toolchain, i never installed the SDK.

3. i run a zephyr blinky sample from the 2.7.0 sdk, i didn't change configuration. Anyone can replicate it.

Eyal.

[Edvin]

Hello Eyal,

I understand. I see that this is actually an issue. I can't replicate it on Windows, but I see that it has been reported on Ubuntu. I will dig a bit more into this, to see if we have any proper workaround.

As a temporary workaround, can you try building your application in 2.8.0? I think it should be able to build the applications from 2.7.0.

Best regards,

Edvin