FATAL ERROR: CMake is not installed or cannot be found; cannot build.

[yuanFang]

Using the 54l15 chip, with the NCSv3.2.1 version, the example is compiled using peripheral_uart.

I have been using this environment for over a year now.

1. When I was compiling today, I encountered the following problem

2. I attempted to delete C:\UserTools\Cmake, but encountered the following error message.

west build --build-dir e:/ncs/low_power_backup/peripheral_uart_update_1/build e:/ncs/low_power_backup/peripheral_uart_update_1 --pristine --board nrf54l15dk/nrf54l15/cpuapp -- -DCONFIG_DEBUG_THREAD_INFO=y

-- west build: generating a build system
FATAL ERROR: CMake is not installed or cannot be found; cannot build.

3. I attempted to reinstall the "NRF Connect for VS Code" within VS Code from scratch.

     FATAL ERROR: CMake is not installed or cannot be found; cannot build.

4. I uninstalled all the extensions of VSCode and finally uninstalled VSCode itself. Then I reinstalled them, but still got an error message.

     FATAL ERROR: CMake is not installed or cannot be found; cannot build.

5. Compile using the nrf connet port



The SDK for my NCS is not on the C drive, but on another drive. I'm not sure if this will cause any problems.The SDK is not on the C drive. I have always used it this way.

Could you please take a look at it and help solve it as soon as possible? It's extremely urgent!

Looking forward to your reply very much.

[Edvin]

Hello,

Can you please try to generate support information:

And paste the output here?

Best regards,

Edvin

[yuanFang]

hello,

thank you for your reply.

When I deleted "E:\nsc", and then re-downloaded a new "toolchains" on the C drive.It can be compiled and built normally.

When I re-added "E:\nsc", and selected "toolchains" as the E drive, the compilation still went smoothly.

After I deleted the "toolchains" folder on the C drive, the problem of being unable to find Cmake occurred.

Looking forward to your reply very much.

Thanks

[Edvin]

Thank you! We are looking into it, and trying to reproduce the issue. 

Question: Does the issue only occur when you use a different drive than the C-drive for the installation of NCS and the toolchain? Or also if you just use a custom location?

Best regards,

Edvin

[yuanFang]

hello,

Thank you for your reply.

This problem will occur when installing on a non-C drive.

as shown blow

I have now rolled back the version. There are no toolchains on the C drive either, and the problem has been resolved.

Thanks

[Edvin]

What I wanted to know if if you have tried installing NCS and the toolchain on the C-drive (can still be a custom path on the C drive) or if it only happens when you install it on the E drive.

BR,
Edvin

[yuanFang]

I haven't tried installing it in a custom path on the C drive.Only custom installation on the E drive

[Edvin]

Hello,

Can you do me a favour? 

Our VS Code team just sent me a debug version of the nRF Connect extension for VS Code.

In your current setup, with the SDK and toolchain in your current location (E drive), can you install this version of the extension, and paste here what you see in the console terminal by following these instructions, using the attached file:

nrf-connect-win32-x64-2026.3.1540.vsix.txt

1: Rename this file (remove ".txt" from the end. I am not allowed to upload .vsix files to DevZone)

2: in VS Code, click the extension window: 

3: Select the 3 dots: 

4: Select "install from VSIX...": 

5: restart VS Code, and make sure the extension is running. Then select "Toggle Developer Tools: 

6: This will open a new window. In there: Select the console tab, right click any of the lines and click "Save as...", save the file, and upload the generated .log file here:

Best regards,

Edvin