Hello,
I installed NCS 2.0.0 via toolchain manager (Windows).
However, if I:
- open a new cmd window
- set ZEPHYR_BASE to <ZEPHYR_NCS_2_0_0_PATH>
- try to build an example within NCS 2.0.0
I see that the project is still using the old toolchain (v1.9.0), installed in another folder:
..\dev\toolchains\ncs\v2.0.0\nrf\samples\bluetooth\peripheral_hids_mouse>west build -b nrf52840dk_nrf52840 --pristine
-- west build: making build dir C:\Users\...\dev\toolchains\ncs\v2.0.0\nrf\samples\bluetooth\peripheral_hids_mouse\build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/Users/.../dev/toolchains/ncs/v2.0.0/nrf/samples/bluetooth/peripheral_hids_mouse
-- Using NCS Toolchain 1.9.0 for building. (C:/Users/.../dev/toolchains/ncs/v1.9.0/toolchain/cmake)
-- Found Python3: C:/Users/.../dev/toolchains/ncs/v1.9.0/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: C:/Users/.../dev/toolchains/ncs/v2.0.0/zephyr/.cache
-- Zephyr version: 3.0.99 (C:/Users/.../dev/toolchains/ncs/v2.0.0/zephyr)
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
...
If instead I try to build using "Open Command Prompt" via Toolchain Manager, things look like working.It looks like the "Open Command Prompt" button is setting a lot of environment variables that are then used by the build system.
In the past (v.1.x.x) it was enough to set ZEPHYR_BASE to a different NCS installation to make sure we were using the right toolchain.
If this is not the case we need all the details to make sure we can build using whatever installed toolchain from any command line front-end (cmd / powershell).
Thanks for your help,
D
