NCS toolchain path missing in VSCode

RE: NCS toolchain path missing in VSCode

Amanda Hsieh — Mon, 21 Nov 2022 20:48:00 GMT

Hi,

Sorry for the delay. The team can't reproduce the errors, however, they are all cmake related and apart from the last minor one they are reported by the cmake extension (we don't control them). The error message is curious though: BOARD is not being defined on the CMake command-line in the environment or by the app. A build cannot be generated by west on the command line without specifying a valid board, and neither it is possible within VS Code (that also just calls west). I'd say these are stale reports and they can be ignored, otherwise, it would be nice to know the exact steps to reproduce.

Regards,
Amanda H.

RE: NCS toolchain path missing in VSCode

HarjitS — Mon, 07 Nov 2022 18:24:22 GMT

I'm not getting any build errors after I deleted the build configuration. Restarted VSCode. Recreated the build configuration and redid the build.

But on startup, I still get:
[{
   "resource": "/C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/extensions.cmake",
   "owner": "cmake-configure-diags",
   "severity": 8,
   "message": "CMake Error at C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/extensions.cmake:2398 (message):BOARD is not being defined on the CMake command-line in the environment or\nby the app.",
   "source": "CMake (message)",
   "startLineNumber": 2398,
   "startColumn": 1,
   "endLineNumber": 2398,
   "endColumn": 10000,
   "relatedInformation": [
       {
           "startLineNumber": 52,
           "startColumn": 1,
           "endLineNumber": 52,
           "endColumn": 1000,
           "message": "In call to 'zephyr_check_cache' here",
           "resource": "/C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/boards.cmake"
       },
       {
           "startLineNumber": 121,
           "startColumn": 1,
           "endLineNumber": 121,
           "endColumn": 1000,
           "message": "In call to 'include' here",
           "resource": "/C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/zephyr_default.cmake"
       },
       {
           "startLineNumber": 66,
           "startColumn": 1,
           "endLineNumber": 66,
           "endColumn": 1000,
           "message": "In call to 'include' here",
           "resource": "/C:/Depot/Source/Library/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake"
       },
       {
           "startLineNumber": 159,
           "startColumn": 1,
           "endLineNumber": 159,
           "endColumn": 1000,
           "message": "In call to 'include_boilerplate' here",
           "resource": "/C:/Depot/Source/Library/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake"
       },
       {
           "startLineNumber": 4,
           "startColumn": 1,
           "endLineNumber": 4,
           "endColumn": 1000,
           "message": "In call to 'find_package' here",
           "resource": "/c:/Depot/Source/nRF/TestApp/peripheral_lbs/CMakeLists.txt"
       }
   ]
},{
   "resource": "/c:/Depot/Source/Library/ncs/v2.1.0/zephyr/CMakeLists.txt",
   "owner": "nrf-connect",
   "severity": 4,
   "message": "__ASSERT() statements are globally ENABLED",
   "source": "cmake",
   "startLineNumber": 1839,
   "startColumn": 1,
   "endLineNumber": 1839,
   "endColumn": 2147483647
}]

RE: NCS toolchain path missing in VSCode

Amanda Hsieh — Thu, 27 Oct 2022 20:54:29 GMT

Do you see any notification after relaunching VScode or building the peripheral_lbs?

Do you still got the same error log while building peripheral_lbs? Try to delete the build folder and build again. Please provide the error log if it still has the issue.

Thanks,
Amanda H.

RE: NCS toolchain path missing in VSCode

HarjitS — Thu, 27 Oct 2022 18:32:12 GMT

Thank for the new suggestion and continuing to help.

I followed your instructions and there were no missing extensions to install.

I looked in the VSCode extension list and I see "nRF Connect for VS Code Extension Pack" with no errors or any issues.

VSCode had no notifications either.

RE: NCS toolchain path missing in VSCode

Amanda Hsieh — Thu, 27 Oct 2022 13:57:28 GMT

Hi,

From the Toolchain Manager, click on the Open VS Code button to install the nRF Connect Extension Pack. You will see a list of any missing extensions that need to be installed.

Click Install missing extensions. Relaunch both the Toolchain Manager and nRF Connect for Desktop to see if any remaining tools still need to be installed.

It will show on the right down corner to ask switch to the nordic extension. Please press YES. You also could Open the nRF Connect extension by clicking its icon or pressing Ctrl+Alt+N.

-Amanda

RE: NCS toolchain path missing in VSCode

HarjitS — Wed, 26 Oct 2022 21:55:04 GMT

I didn't dismissed or ignored any prompts. I re-installed VSCode using Toolchain manager as suggested and it didn't fix the issue.

The reason the CMake extension is saying this is that the build environment is not able to find the NCS one because the environment isn't setup properly which is the issue I need your help to fix.

RE: NCS toolchain path missing in VSCode

Amanda Hsieh — Mon, 24 Oct 2022 14:21:47 GMT

Hi,

This looks like the CMake extension. VS Code warns them that the cmake extension isn't compatible with the nordic extension every time it starts up, but you have probably just dismissed or ignored it. They should build using Nordic's extension: https://nrfconnect.github.io/vscode-nrf-connect/connect/build_app_ncs.html

-Amanda

RE: NCS toolchain path missing in VSCode

HarjitS — Fri, 21 Oct 2022 20:12:59 GMT

I followed the instructions and I uninstalled VSCode. Ran nRF Connect for Desktop and then Toolchain Manager which told me to install VSCode. I installed VS Code.

In the Terminal, the path doesn't include the ncs toolchain. I get the same result as my first post.

The command prompt from Toolchain Manager includes the ncs toolchain path.

Here is the contents of the OUTPUT tab from VSCode:

[variant] Loaded new set of variants
[kit] Successfully loaded 6 kits from C:\Users\HarjitS\AppData\Local\CMakeTools\cmake-tools-kits.json
[variant] Loaded new set of variants
[variant] Loaded new set of variants
[proc] The command: ninja --version failed with error: Error: spawn ninja ENOENT
[proc] The command: ninja-build --version failed with error: Error: spawn ninja-build ENOENT
[proc] The command: ninja --version failed with error: Error: spawn ninja ENOENT
[proc] The command: ninja-build --version failed with error: Error: spawn ninja-build ENOENT
[proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -Sc:/Depot/Source/nRF/TestApp/peripheral_lbs -Bc:/Depot/Source/nRF/TestApp/peripheral_lbs/build -G "Unix Makefiles"
[proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -Sc:/Depot/Source/nRF/TestApp/myfirstapp -Bc:/Depot/Source/nRF/TestApp/myfirstapp/build -G "Unix Makefiles"
[proc] The command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -Sc:/Depot/Source/nRF/TestApp/peripheral_lbs -Bc:/Depot/Source/nRF/TestApp/peripheral_lbs/build -G "Unix Makefiles" exited with code: 1 and signal: null
[main] Configuring folder: peripheral_lbs 
[proc] The command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -Sc:/Depot/Source/nRF/TestApp/myfirstapp -Bc:/Depot/Source/nRF/TestApp/myfirstapp/build -G "Unix Makefiles" exited with code: 1 and signal: null
[main] Configuring folder: myfirstapp 
[proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -Sc:/Depot/Source/nRF/TestApp/peripheral_lbs -Bc:/Depot/Source/nRF/TestApp/peripheral_lbs/build -G "Unix Makefiles"
[cmake] Not searching for unused variables given on the command line.
[cmake] Loading Zephyr default modules (Zephyr base (cached)).
[cmake] -- Application: C:/Depot/Source/nRF/TestApp/peripheral_lbs
[proc] Executing command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_C_COMPILER:FILEPATH=C:\Depot\Source\Library\ncs\toolchains -Sc:/Depot/Source/nRF/TestApp/myfirstapp -Bc:/Depot/Source/nRF/TestApp/myfirstapp/build -G "Unix Makefiles"
[cmake] -- Using NCS Toolchain 2.1.0 for building. (C:/Depot/Source/Library/ncs/toolchains/v2.1.0/cmake)
[cmake] Not searching for unused variables given on the command line.
[cmake] Loading Zephyr default modules (Zephyr base (cached)).
[cmake] -- Application: C:/Depot/Source/nRF/TestApp/myfirstapp
[cmake] -- Using NCS Toolchain 2.1.0 for building. (C:/Depot/Source/Library/ncs/toolchains/v2.1.0/cmake)
[cmake] -- Cache files will be written to: C:/Depot/Source/Library/ncs/v2.1.0/zephyr/.cache
[cmake] -- Zephyr version: 3.1.99 (C:/Depot/Source/Library/ncs/v2.1.0/zephyr)
[cmake] -- Cache files will be written to: C:/Depot/Source/Library/ncs/v2.1.0/zephyr/.cache
[cmake] -- Zephyr version: 3.1.99 (C:/Depot/Source/Library/ncs/v2.1.0/zephyr)
[cmake] -- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
[cmake] -- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
[cmake] CMake Error at C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/extensions.cmake:2398 (message):
[cmake]   BOARD is not being defined on the CMake command-line in the environment or
[cmake]   by the app.
[cmake] Call Stack (most recent call first):
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/boards.cmake:52 (zephyr_check_cache)
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/zephyr_default.cmake:121 (include)
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
[cmake]   CMakeLists.txt:4 (find_package)
[cmake] 
[cmake] 
[cmake] -- Configuring incomplete, errors occurred!
[cmake] See also "C:/Depot/Source/nRF/TestApp/peripheral_lbs/build/CMakeFiles/CMakeOutput.log".
[cmake] See also "C:/Depot/Source/nRF/TestApp/peripheral_lbs/build/CMakeFiles/CMakeError.log".
[proc] The command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -Sc:/Depot/Source/nRF/TestApp/peripheral_lbs -Bc:/Depot/Source/nRF/TestApp/peripheral_lbs/build -G "Unix Makefiles" exited with code: 1 and signal: null
[cmake] CMake Error at C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/extensions.cmake:2398 (message):
[cmake]   BOARD is not being defined on the CMake command-line in the environment or
[cmake]   by the app.
[cmake] Call Stack (most recent call first):
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/boards.cmake:52 (zephyr_check_cache)
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/cmake/modules/zephyr_default.cmake:121 (include)
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
[cmake]   C:/Depot/Source/Library/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
[cmake]   CMakeLists.txt:4 (find_package)
[cmake] 
[cmake] 
[cmake] -- Configuring incomplete, errors occurred!
[cmake] See also "C:/Depot/Source/nRF/TestApp/myfirstapp/build/CMakeFiles/CMakeOutput.log".
[cmake] See also "C:/Depot/Source/nRF/TestApp/myfirstapp/build/CMakeFiles/CMakeError.log".
[proc] The command: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_C_COMPILER:FILEPATH=C:\Depot\Source\Library\ncs\toolchains -Sc:/Depot/Source/nRF/TestApp/myfirstapp -Bc:/Depot/Source/nRF/TestApp/myfirstapp/build -G "Unix Makefiles" exited with code: 1 and signal: null
[driver] Switching to kit: nRF Zephyr Toolchain
[proc] The command: ninja --version failed with error: Error: spawn ninja ENOENT
[proc] The command: ninja-build --version failed with error: Error: spawn ninja-build ENOENT

RE: NCS toolchain path missing in VSCode

Amanda Hsieh — Fri, 21 Oct 2022 14:44:24 GMT

Try to remover the VS code and let the Toolchain Manager to install the VS Code. See Installing nRF Connect for VS Code extension.

-Amanda

RE: NCS toolchain path missing in VSCode

HarjitS — Thu, 20 Oct 2022 22:07:22 GMT

Thank you for the quick response but that doesn't address/fix the issue.

In the "Set up the command-line..." page it says to navigate to the ncs folder and run the zephyr\zephyr-env.cmd script.

The path is incorrect. There is no zephyr folder in the ncs directory. It is now ncs\<version>\zephyr

I did run the zephyr-env.cmd in the terminal and it did nothing to the path.

The zephyr-env.cmd script is:

@echo off
set ZEPHYR_BASE=%~dp0

if exist "%userprofile%\zephyrrc.cmd" (
call "%userprofile%\zephyrrc.cmd"
)

and there is no zephyrrc.cmd file in the %userprofile% directory or anywhere on my computer.

RE: NCS toolchain path missing in VSCode

Amanda Hsieh — Thu, 20 Oct 2022 20:48:16 GMT

Hi,

Take a look at this section and set up the Set up the command-line build environment.

Actually, you don't need to install VS Code manually. Toolchain Manager can install automatically. See Installing nRF Connect for VS Code extension.

Regards,
Amanda