SDK v2.5.99-dev1 has many compile errors

Question

Hello, 
 I am working on a Mac mini, Apple M2 chipset, macOS Sonoma 14.2.1. I am using Visual Studio Code Version: 1.86.2 (Universal) Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda Date: 2024-02-13T19:42:13.651Z Electron: 27.2.3 ElectronBuildId: 26908389 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.2.0 
 I have been developing code on the nRF52840 DK for several months using SDK v2.5.0. I recently downloaded SDK v2.5.99-dev1 
 After successfully building with SDK v2.5.0, I remove the build directory, change the active SDK to 2.5.99-dev1, create a new Build configuration (the same way I did for v2.5.0 SDK), and then build. I get many compile errors like this: 
 ../../../../../../../opt/nordic/ncs/v2.5.99-dev1/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/cluster-objects.cpp: In member function 'CHIP_ERROR chip::app::Clusters::UnitTesting::Structs::TestFabricScoped::DecodableType::Decode(chip::TLV::TLVReader&)': ../../../../../../../opt/nordic/ncs/v2.5.99-dev1/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/cluster-objects.cpp:20334:37: error: 'class chip::app::Clusters::detail::StructDecodeIterator' has no member named 'Next' 20334 | auto __element = __iterator.Next(); | ^~~~ ../../../../../../../opt/nordic/ncs/v2.5.99-dev1/modules/lib/matter/zzz_generated/app-common/app-common/zap-generated/cluster-objects.cpp:20335:18: error: 'holds_alternative' is not a member of 'std' 20335 | if (std::holds_alternative<CHIP_ERROR>(__element)) | ^~~~~~~~~~~~~~~~~

Gene Roylance · Accepted Answer

Andreas, 
 Sorry for the delay, but I believe that I have found the solution to the problem that I have been experiencing. First, let me answer you last two questions: 
 1) Does the JLink version make a different? Answer: No, downgrading to 7.88j made no difference. 
 2) Does the Toolschain path in the Config setting need to be something other than a null string? Answer Not apparently, I changed the setting to what Steve had ("${nrf-connect.toolchain:2.6.0}") and it made no difference. 
 So, this is how I fixed my problem. Steve and I were comparing our $HOME/.zprofile files and I noticed that I had some unique lines (as compared to his .zprofie file): # SDK v2.6.0 export PATH="$PATH:/opt/nordic/ncs/toolchains/580e4ef81c/bin" # SDK v2.5.0 #export PATH="$PATH:/opt/nordic/ncs/toolchains/20d68df7e5/bin" # SDK v2.4.1 #export PATH="$PATH:/opt/nordic/ncs/toolchains/4ef6631da0/bin" # nrfutil tools export PATH="$PATH:/Users/puzl/Library/Python/3.9/bin" 
 First, I commented out the SDK v2.6.0 toolschains path addition, but that made no difference. Next, I commented out the nrfutil tools PATH command, and again no difference. However, I was a bit curious about the nrfutil tools. I noticed that it had some python applications AND some python libraries included in this tool. I also noticed that the version of this utility was quite old (nrfutil version 5.2.0) whereas the latest version was 7.7.0. 
 I am not sure where this old version of nrfutil came from, but I did recall that I was trying several versions of the nrfutil tool trying to program a nRF52940 USB dongle device last November. I finally resorted to using the windows version of the tool to complete the dongle programming, but I left the nrfutil tool on my Mac machine (and in my path). I would guess that this tool was conflicting with the v2.6.0 SDK or toolchains. 
 I would like to point out that I had to remove the v2.6.0 SDK and toolchains and then re-install them after I had removed the nrfutil tool (bin and lib) files from my machine to totally fix the problem. 
 I would also like to point out one additional issue that I found on my M2 Mac. When I used the Toolchain Manager v1.3.1 (initiated from the nRF Connect for Desktop v4.4.1 application) to try and re-install the v2.6.0 SDK and toolchains, it was downloading the ncs-toolchain- x86_64 -macos-580e4ef81c.tar.gz file instead of the ncs-toolchain- aarch64 -macos-580e4ef81c.tar.gz file that the nRF Connect extension of Visual Studio Code downloaded (I switched to the VS code installation after the Toolchain Manager failed). The Toolchain Manager v1.3.1 toolchains installation hung (did not complete), which tipped me off to this difference. 
 One last thing, I was also able to find the answer to the original question that prompted this ticket. I was able to get the v2.5.99-dev1 SDK to build on an existing project by changing this line in the prj.conf file: -CONFIG_STD_CPP14=y +CONFIG_STD_CPP17=y 
 Best Regards, 
 Gene

SDK v2.5.99-dev1 has many compile errors

Top Replies