Build fails for matter samples with nrf5340-DK

Hi, I can successfully build the openthread-cli sample but fail with all matter samples

Please refer the following log


> Executing task: nRF Connect: Build: light_bulb/build (active) <

Building light_bulb
west build --build-dir d:\myWork\Research\matter\prog\light_bulb\build d:\myWork\Research\matter\prog\light_bulb

[0/91] Performing build step for 'chip-gn'
Generating compile_commands took 16ms
Done. Made 77 targets from 84 files in 115ms
ninja: error: objd:\src\access\access.ninja:9: expected newline, got ':'

FAILED: modules/connectedhomeip/src/chip-gn-stamp/chip-gn-build modules/connectedhomeip/-lCHIP
cmd.exe /C "cd /D D:\myWork\Research\matter\prog\light_bulb\build\modules\connectedhomeip && C:\ncs\toolchains\v2.0.0\opt\bin\python.exe C:/ncs/v2.0.0/modules/lib/matter/config/nrfconnect/chip-module/make_gn_args.py @args.tmp > args.gn && C:/ncs/toolchains/v2.0.0/opt/bin/gn.exe --root=C:/ncs/v2.0.0/modules/lib/matter --root-target=C:/ncs/v2.0.0/modules/lib/matter/config/nrfconnect/chip-gn --dotfile=C:/ncs/v2.0.0/modules/lib/matter/config/nrfconnect/chip-gn/.gn --script-executable=C:/ncs/toolchains/v2.0.0/opt/bin/python.exe --export-compile-commands gen --check --fail-on-unused-args . && ninja"
[2/91] cmd.exe /C "cd /D D:\myWork\Research\matter\prog\light_bulb\build\modules\openthread\build && C:\ncs\toolchains\v2.0.0\opt\bin\cmake.exe -DLIST="OPENTHREAD_CONFIG_ASSERT_ENABLE=1;OPENTHREAD_CONFIG_BACKBONE_ROUTER_DUA_NDPROXYING_ENABLE=0;OPENTHREAD_CONFIG_BACKBONE_ROUTER_MULTICAST_ROUTING_ENABLE=0;OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS=0;OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS_MANAGEMENT=0;OPENTHREAD_CONFIG_CHILD_SUPERVISION_ENABLE=1;OPENTHREAD_CONFIG_COAP_API_ENABLE=1;OPENTHREAD_CONFIG_MAC_CSL_AUTO_SYNC_ENABLE=0;OPENTHREAD_CONFIG_DHCP6_CLIENT_ENABLE=1;OPENTHREAD_CONFIG_DNS_CLIENT_ENABLE=1;OPENTHREAD_CONFIG_ECDSA_ENABLE=1;OPENTHREAD_CONFIG_SRP_CLIENT_ENABLE=1;OPENTHREAD_CONFIG_DUA_ENABLE=1;OPENTHREAD_CONFIG_MLR_ENABLE=1;OPENTHREAD_CONFIG_HEAP_EXTERNAL_ENABLE=1;OPENTHREAD_CONFIG_IP6_FRAGMENTATION_ENABLE=1;OPENTHREAD_CONFIG_JOINER_ENABLE=1;OPENTHREAD_CONFIG_MLE_LINK_METRICS_INITIATOR_ENABLE=1;OPENTHREAD_CONFIG_MLE_LINK_METRICS_SUBJECT_ENABLE=1;OPENTHREAD_CONFIG_TMF_NETWORK_DIAG_MTD_ENABLE=1;OPENTHREAD_CONFIG_PING_SENDER_ENABLE=1;OPENTHREAD_CONFIG_IP6_SLAAC_ENABLE=1;OPENTHREAD_CONFIG_SNTP_CLIENT_ENABLE=1;OPENTHREAD_SPINEL_CONFIG_RCP_RESTORATION_MAX_COUNT=0;PACKAGE_NAME="OPENTHREAD";OPENTHREAD_CONFIG_THREAD_VERSION=OT_THREAD_VERSION_1_2;OPENTHREAD_CONFIG_NCP_HDLC_ENABLE=1;KERNEL;__ZEPHYR__=1;_FORTIFY_SOURCE=2;__LINUX_ERRNO_EXTENSIONS__;USE_PARTITION_MANAGER=1;ZCBOR_ASSERT;__PROGRAM_START;NRF5340_XXAA_APPLICATION;NRF_SKIP_FICR_NS_COPY_TO_RAM;NRF_802154_USE_RAW_API=1;NRF_802154_PENDING_SHORT_ADDRESSES=;NRF_802154_PENDING_EXTENDED_ADDRESSES=;NRF_802154_RX_BUFFERS=16;NRF_802154_TX_STARTED_NOTIFY_ENABLED=1;NRF_802154_ACK_TIMEOUT_ENABLED=1;NRF_802154_ENCRYPTION_ENABLED=1;NRF_802154_SECURITY_WRITER_ENABLED=1;NRF_802154_IE_WRITER_ENABLED=1;NRF_802154_INTERNAL_RADIO_IRQ_HANDLING=0;NRF_802154_ECB_PRIORITY=-1;NRF_802154_SWI_PRIORITY=1;MBEDTLS_CONFIG_FILE="nrf-config.h";MBEDTLS_USER_CONFIG_FILE="nrf-config-user.h"" -P C:/ncs/v2.0.0/modules/lib/openthread/etc/cmake/print.cmake"
OPENTHREAD_CONFIG_ASSERT_ENABLE=1
OPENTHREAD_CONFIG_BACKBONE_ROUTER_DUA_NDPROXYING_ENABLE=0
OPENTHREAD_CONFIG_BACKBONE_ROUTER_MULTICAST_ROUTING_ENABLE=0
OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS=0
OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS_MANAGEMENT=0
OPENTHREAD_CONFIG_CHILD_SUPERVISION_ENABLE=1
OPENTHREAD_CONFIG_COAP_API_ENABLE=1
OPENTHREAD_CONFIG_MAC_CSL_AUTO_SYNC_ENABLE=0
OPENTHREAD_CONFIG_DHCP6_CLIENT_ENABLE=1
OPENTHREAD_CONFIG_DNS_CLIENT_ENABLE=1
OPENTHREAD_CONFIG_ECDSA_ENABLE=1
OPENTHREAD_CONFIG_SRP_CLIENT_ENABLE=1
OPENTHREAD_CONFIG_DUA_ENABLE=1
OPENTHREAD_CONFIG_MLR_ENABLE=1
OPENTHREAD_CONFIG_HEAP_EXTERNAL_ENABLE=1
OPENTHREAD_CONFIG_IP6_FRAGMENTATION_ENABLE=1
OPENTHREAD_CONFIG_JOINER_ENABLE=1
OPENTHREAD_CONFIG_MLE_LINK_METRICS_INITIATOR_ENABLE=1
OPENTHREAD_CONFIG_MLE_LINK_METRICS_SUBJECT_ENABLE=1
OPENTHREAD_CONFIG_TMF_NETWORK_DIAG_MTD_ENABLE=1
OPENTHREAD_CONFIG_PING_SENDER_ENABLE=1
OPENTHREAD_CONFIG_IP6_SLAAC_ENABLE=1
OPENTHREAD_CONFIG_SNTP_CLIENT_ENABLE=1
OPENTHREAD_SPINEL_CONFIG_RCP_RESTORATION_MAX_COUNT=0
PACKAGE_NAME=OPENTHREAD
OPENTHREAD_CONFIG_THREAD_VERSION=OT_THREAD_VERSION_1_2
OPENTHREAD_CONFIG_NCP_HDLC_ENABLE=1
KERNEL
__ZEPHYR__=1
_FORTIFY_SOURCE=2
_LINUX_ERRNO_EXTENSIONS_
USE_PARTITION_MANAGER=1
ZCBOR_ASSERT
__PROGRAM_START
NRF5340_XXAA_APPLICATION
NRF_SKIP_FICR_NS_COPY_TO_RAM
NRF_802154_USE_RAW_API=1
NRF_802154_PENDING_SHORT_ADDRESSES=
NRF_802154_PENDING_EXTENDED_ADDRESSES=
NRF_802154_RX_BUFFERS=16
NRF_802154_TX_STARTED_NOTIFY_ENABLED=1
NRF_802154_ACK_TIMEOUT_ENABLED=1
NRF_802154_ENCRYPTION_ENABLED=1
NRF_802154_SECURITY_WRITER_ENABLED=1
NRF_802154_IE_WRITER_ENABLED=1
NRF_802154_INTERNAL_RADIO_IRQ_HANDLING=0
NRF_802154_ECB_PRIORITY=-1
NRF_802154_SWI_PRIORITY=1
MBEDTLS_CONFIG_FILE=nrf-config.h
MBEDTLS_USER_CONFIG_FILE=nrf-config-user.h
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'c:\ncs\toolchains\v2.0.0\opt\bin\cmake.EXE' --build 'd:\myWork\Research\matter\prog\light_bulb\build'
The terminal process terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.

nRF Connect SDK 2.0.0
windows10
nRF5340-DK

Parents
  • Thanks, Kai! One thing that my eyes caught immediately is that your toolchain is installed on C;\ and compiling applications from there appears to work as expected. The applications that you would like to compile in VS Code however are located on D:\.  

    That might be an issue, especially when third-party software is involved. I’m not sure at this point if the VS Code extension is designed to support this. 

    FYI: Since many of my colleagues currently are out of office due to summer vacation period in Norway, you have to expect delayed answers from my side. My apologies for the inconvenience! 

    Cheers, 

    Markus 

Reply
  • Thanks, Kai! One thing that my eyes caught immediately is that your toolchain is installed on C;\ and compiling applications from there appears to work as expected. The applications that you would like to compile in VS Code however are located on D:\.  

    That might be an issue, especially when third-party software is involved. I’m not sure at this point if the VS Code extension is designed to support this. 

    FYI: Since many of my colleagues currently are out of office due to summer vacation period in Norway, you have to expect delayed answers from my side. My apologies for the inconvenience! 

    Cheers, 

    Markus 

Children
No Data
Related