Build matter sample FAILED on newest NCS SDK 2.7.0

RE: Build matter sample FAILED on newest NCS SDK 2.7.0

Charlie — Tue, 10 Sep 2024 10:31:54 GMT

I do not think so. You can verify sysbuild from building log, "sysbuild_default" is the keyword when sysbuild is used.

Building matter_lock
west build --build-dir /opt/nordic/ncs/v2.7.0/nrf/matter_lock/build /opt/nordic/ncs/v2.7.0/nrf/matter_lock --pristine --board nrf5340dk/nrf5340/cpuapp -- -DNCS_TOOLCHAIN_VERSION=NONE
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /opt/nordic/ncs/toolchains/f8037e9b83/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/cs/Library/Caches/zephyr

I think inside the SDK means nrf folder. You can find the following definition in nrf/CMakeLists.txt

zephyr_get(NCS_RUNNER_${runner_ext} SYSBUILD)

Best regards,

Charlie

RE: Build matter sample FAILED on newest NCS SDK 2.7.0

Aaron — Tue, 10 Sep 2024 09:44:45 GMT

Hi Charlie,

Thank you for the response,
After checking the option 'sysbuild', the build process is successful.

Another question, where is the boundary of SDK?
My project is located at "ncs\v2.7.0\projects", is it outside the SDK?

RE: Build matter sample FAILED on newest NCS SDK 2.7.0

Charlie — Tue, 10 Sep 2024 09:08:36 GMT

Hi Aaron,

If you are using VS Code to do building configuration. Please make sure "Use sysbuild" option is checked.

It is stated in nRF Connect SDK v2.7.0 Release Notes (nordicsemi.com):

All samples and applications in the SDK are built with sysbuild by default. Applications that are outside the SDK are not built with sysbuild by default.

Best regards,

Charlie