Building sample apps using CLI and SDK v3 fails

RE: Building sample apps using CLI and SDK v3 fails

I.gin — Wed, 12 Nov 2025 14:50:36 GMT

This one solved it. Removed the pyenv directory from PATH and also the python installed by homebrew and was set as default, Now I can build the app using command line.
Thanks! :)

RE: Building sample apps using CLI and SDK v3 fails

Priyanka — Wed, 12 Nov 2025 13:35:30 GMT

Could you then try removing all other python installation in your PATH as mentioned in this ticket. Because then CMake will pickup the default ones within the toolchains, possibly at C:/ncs/toolchains/<toolchain_version>/opt/bin/python.exe

-Priyanka

RE: Building sample apps using CLI and SDK v3 fails

I.gin — Wed, 12 Nov 2025 13:14:32 GMT

All the tests are done by opening a terminal with the corresponding SDK and toolchain version. It also shows at the beginning of the logs that I posted.

If I don't do that and use command in a terminal without SDK and Toolchain I get "command not found" error.

RE: Building sample apps using CLI and SDK v3 fails

Priyanka — Wed, 12 Nov 2025 12:19:55 GMT

Hi,

Could you try opening the terminal profile corresponding to the proper NCS version? For eg. , if you are trying with v3.1.1, first select "open termina profile"

then select the correct SDK and Toolchain version:

This will open up a terminal and try building in that:

-Priyanka

RE: Building sample apps using CLI and SDK v3 fails

I.gin — Wed, 12 Nov 2025 10:23:34 GMT

Tested this and still getting the same error.

RE: Building sample apps using CLI and SDK v3 fails

Priyanka — Wed, 12 Nov 2025 09:49:04 GMT

Hi,

The issue is because your CMake is picking up the external pyenv Python version and not the NCS Toolchain's python. You could make try to point CMake to the NCS Toolchain's python:

west build -b nrf9160dk/nrf9160/ns --pristine \
-- -DPython3_EXECUTABLE=/opt/nordic/ncs/toolchains/0b393f9e1b/opt/python@3.12/bin/python3.12

Please do let me know if this works.

-Priyanka