• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 90 subscribers
  • Views 3153 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 283902
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF Connect SDK VS code extension and ZEPHYR_BASE

sread

Is it possible to override ZEPHYR_BASE when building with the nRF Connect extension in VS code? 

I am using workflow 4 (application as manifest repository) and can build successfully with scripts on the command line that manually set ZEPHYR_BASE, ZEPHYR_TOOLCHAIN_VARIANT and GNUARMEMB_TOOLCHAIN_PATH. The basic project layout is as follows:

  • my workspace
    • my_application
      • inc/
      • src/ 
      • prj.conf
      • west.yml
    • ncs
      • nrf
      • zephyr
      • ...
    • ...

 It seems to be looking in my workspace root for a zephyr folder that doesn't exist. 

> Executing task: nRF Connect: Build nrf-connect/build (active) <

Building ant_lib
west build --build-dir c:\<my workspace>\build c:\<my_workspace>\<my application> --pristine --board nrf5340dk_nrf5340_cpunet -- -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=On -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DCONF_FILE:STRING="c:/<my workspace>/<my application>/prj.conf" -DDTC_OVERLAY_FILE:STRING="c:/<my workspace>/<my application>/nrf5340dk_nrf5340_cpunet.overlay"

-- west build: generating a build system
Including boilerplate (Zephyr base): C:/<my workspace>/zephyr/cmake/app/boilerplate.cmake
CMake Error at C:\<my ncs toolchain>\ncs\v1.8.0\zephyr\share\zephyr-package\cmake\ZephyrConfig.cmake:24 (include):
  include could not find requested file:

    C:/<my workspace>/zephyr/cmake/app/boilerplate.cmake

I was hopeful I could use the west.env variable in my code-workspace file like this but it didn't have any effect.
"nrf-connect.topdir": "${workspaceFolder}\\ncs",
"nrf-connect.west.env": {
            "$base": "process",
            "ZEPHYR_BASE": "${workspaceFolder}\\ncs\\zephyr",
            "ZEPHYR_TOOLCHAIN_VARIANT": "gnuarmemb",
            "GNUARMEMB_TOOLCHAIN_PATH": "<my compiler path>
        }
I am using NCS v1.8.0, nRF Connect for VS Code v2022.1.192.
Is this supported?
  • 0

    Hello,

    you can change the nrf-connect.topdir setting as explained here.

  • 0 in reply to Hakon

    I tried that as shown in my post above (both using ${workspaceFolder}\\ncs and an absolute path to that folder). The paths I am setting are showing up as expected in the Extension settings. But they are not being respected when I create a build configuration. West is attempting to find a file here: 

    C:/<my workspace>/zephyr/cmake/app/boilerplate.cmake

    When it is actually located here: 

    C:/<my workspace>/ncs/zephyr/cmake/app/boilerplate.cmake

  • 0 in reply to sread

    If this doesn't work, then I'm not sure what the correct way to do this is. I will ask about this internally.

  • +1

    This could be a bug in the vs code extension. It has been reported.

    Until it's fixed, you can try using a multi-root workspace instead by

    • Opening "my_application" as a folder in vs code.
    • Click "File"->"add folder to workspace" and add "ncs"
    • Use absolute paths in settings
Related