<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116679/updating-the-sdk-to-2-8-0-resulting-in-non-working-cmake-compilation</link><description>I have a sample app (hellow world from the zephyr samples). 
 It compiled well on my system in vscode using 2.7.0 and sysbuild. 
 I then installed 2.8.0 and suddenly the build fails, the cmake cannot find the python libraries. 
 The reason seemed to be</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 30 Nov 2024 18:49:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116679/updating-the-sdk-to-2-8-0-resulting-in-non-working-cmake-compilation" /><item><title>RE: updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/thread/512849?ContentTypeID=1</link><pubDate>Sat, 30 Nov 2024 18:49:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db68e50a-2de8-4999-b09d-6228536db191</guid><dc:creator>Eyal_Gal</dc:creator><description>&lt;p&gt;thanks Edvin! i will put this to the test tomorrow and report back.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/thread/512644?ContentTypeID=1</link><pubDate>Thu, 28 Nov 2024 21:34:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5090b8f1-b278-41ad-8700-95178bbd4702</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello again,&lt;/p&gt;
&lt;p&gt;It seems this bug was indeed fixed, but it requires you to check out a different commit than the standard 2.7.0.&lt;/p&gt;
&lt;p&gt;IF you want to build v2.7.0 while having the v2.8.0 toolchain present, and trying to specify the NCS_TOOLCHAIN_VERSION, then you need to use this commit:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/nrfconnect/sdk-nrf/commit/c256a1d5f3e7c8cdd6c874d9ff114ff22fb142df"&gt;https://github.com/nrfconnect/sdk-nrf/commit/c256a1d5f3e7c8cdd6c874d9ff114ff22fb142df&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For more details, please check:&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/17399"&gt;https://github.com/nrfconnect/sdk-nrf/pull/17399&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/thread/512609?ContentTypeID=1</link><pubDate>Thu, 28 Nov 2024 14:31:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:68a49b40-0f05-471a-8973-e1ca0ff38bed</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Eyal,&lt;/p&gt;
&lt;p&gt;I understand. I see that this is actually an issue. I can&amp;#39;t replicate it on Windows, but I see that it has been reported on Ubuntu. I will dig a bit more into this, to see if we have any proper workaround.&lt;/p&gt;
&lt;p&gt;As a temporary workaround, can you try building your application in 2.8.0? I think it should be able to build the applications from 2.7.0.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/thread/512159?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 14:11:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4b1cd1a-3b3e-4946-8ed0-5fb28a90029b</guid><dc:creator>Eyal_Gal</dc:creator><description>&lt;p&gt;Hi Edvin!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Please check above i have described in details how i installed things from scratch on a VM with ubuntu 22.04.5.&lt;br /&gt;as for your questions:&lt;/p&gt;
&lt;p&gt;1. i installed all toolchains and SDKs using vs code plugin.&lt;/p&gt;
&lt;p&gt;2. i have installed 2.7.0 first and then i installed JUST the 2.8.0 toolchain, i never installed the SDK.&lt;/p&gt;
&lt;p&gt;3. i run a zephyr blinky sample from the 2.7.0 sdk, i didn&amp;#39;t change configuration. Anyone can replicate it.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Eyal.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/thread/512114?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 13:03:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c171513b-b065-4bef-aadb-68448bcccb04</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I am sorry for the late reply. How did you install NCS and the toolchain?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is it possible to upload the application that triggers this issue, so that I may have a look, and see if I can replicate the issue or not?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: updating the SDK to 2.8.0 resulting in non working cmake compilation.</title><link>https://devzone.nordicsemi.com/thread/511791?ContentTypeID=1</link><pubDate>Sun, 24 Nov 2024 20:18:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6cc58019-f286-461d-82f6-81db3de553c2</guid><dc:creator>Eyal_Gal</dc:creator><description>&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;eyal@eyal-ThinkPad-P15v-Gen-1:~/develop/scms/staging_area/dali_sniffer$ west build --build-dir /home/eyal/develop/scms/staging_area/dali_sniffer/build /home/eyal/develop/scms/staging_area/dali_sniffer --sysbuild --pristine -c --board nrf52_adafruit_feather/nrf52832 -- -DNCS_TOOLCHAIN_VERSION=&amp;quot;v2.7.0&amp;quot;
-- west build: making build dir /home/eyal/develop/scms/staging_area/dali_sniffer/build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /home/eyal/ncs/toolchains/e9dba88316/usr/local/bin/python3.9 (found suitable version &amp;quot;3.9.18&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/eyal/.cache/zephyr
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: nrf52_adafruit_feather, qualifiers: nrf52832
Parsing /home/eyal/ncs/v2.7.0/zephyr/share/sysbuild/Kconfig
Loaded configuration &amp;#39;/home/eyal/develop/scms/staging_area/dali_sniffer/build/_sysbuild/empty.conf&amp;#39;
Merged configuration &amp;#39;/home/eyal/develop/scms/staging_area/dali_sniffer/build/_sysbuild/empty.conf&amp;#39;
Configuration saved to &amp;#39;/home/eyal/develop/scms/staging_area/dali_sniffer/build/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/eyal/develop/scms/staging_area/dali_sniffer/build/_sysbuild/autoconf.h&amp;#39;
-- 
   **********************************
   * Running CMake for dali_sniffer *
   **********************************

Loading Zephyr default modules (Zephyr base).
-- Application: /home/eyal/develop/scms/staging_area/dali_sniffer
-- CMake version: 3.21.0
-- Using NCS Toolchain 2.8.20241106.790718371940 for building. (/home/eyal/ncs/toolchains/b81a7cd864/cmake)
CMake Error at /home/eyal/ncs/toolchains/e9dba88316/usr/local/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Python3 (missing: Interpreter) (Required is at least version
  &amp;quot;3.8&amp;quot;)
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Also i&amp;#39;ve verified the issue with a fresh new install on vm with ubuntu 22.04.5:&lt;br /&gt;installed vscode with the extensions.&lt;/p&gt;
&lt;p&gt;installed nrf command line tools&lt;/p&gt;
&lt;p&gt;installed nrfutil&lt;/p&gt;
&lt;p&gt;installed from vscode extension the ncs 2.7.0 toolchain and sdk.&lt;/p&gt;
&lt;p&gt;installed from vscode extension the ncs 2.8.0 toolchain.&lt;/p&gt;
&lt;p&gt;Made sure the extension shows clearly it uses 2.7.0 for sdk AND toolchain (set active).&lt;/p&gt;
&lt;p&gt;opened in vscode the zephyr blinky sample&lt;/p&gt;
&lt;p&gt;created a build config using vscode extension for nrf52832 (adafruit) with debug symbols using sysbuild.&lt;/p&gt;
&lt;p&gt;The build fails, it does&amp;nbsp; starts out with the 2.7.0 toolchain but when it get to --using ncs version... it shows it chose 2.8 toolchain.&lt;br /&gt;&lt;br /&gt;Another edit:&lt;/p&gt;
&lt;p&gt;So i&amp;#39;m building using sysbuild and not a regular build so cmake is calling sysbuild and not my cmake right away. i found the sysbuild script that was bing called and added:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;message&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;&amp;quot;@@@@@@@ NCS_TOOLCHAIN_VERSION: ${NCS_TOOLCHAIN_VERSION}&amp;quot;&lt;/span&gt;&lt;span&gt;)&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;it prints &amp;quot;NONE&amp;quot; or v2.7.0 whatever i pass in -D.&lt;/div&gt;
&lt;div&gt;but when i add the same print in my CMakeLists.txt, ${&lt;span&gt;NCS_TOOLCHAIN_VERSION&lt;/span&gt;} is empty. That means the sysbuild does not pass my -D variable on to my cmake file and thus to my zephyr build, so i tried to add name space like blinky_&lt;span&gt;NCS_TOOLCHAIN_VERSION=NONE but it did not help.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;last update, i&amp;#39;m stopping my research with that...&lt;br /&gt;i set NCS_TOOLCHAIN_VERSION to 2.7.0 in my CMakeLists.txt so i know it is taken into account in my build.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;but now it fails in the findpackage call, like before, it tries to use python from 2.8.0 toolchain while all pathes are pointing to 2.7.0 toolchain.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="text"&gt;Loading Zephyr default modules (Zephyr base (cached)).
-- Application: /home/eyal/ncs/v2.7.0/zephyr/samples/basic/blinky
-- CMake version: 3.21.0
##### NCS_TOOLCHAIN_VERSION: 2.7.0
setting minium version to the required version
will try to find package
CMake Error at /home/eyal/ncs/toolchains/e9dba88316/usr/local/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find Python3 (missing: Interpreter) (Required is at least version
  &amp;quot;3.8&amp;quot;)

      Reason given by package: 
          Interpreter: Cannot run the interpreter &amp;quot;/home/eyal/ncs/toolchains/b81a7cd864/usr/local/bin/python3&amp;quot;&lt;/pre&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>