<?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>v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/72187/v1-5-0-mcuboot-build-fail</link><description>Hi, 
 after migrating functional project to latest ncs version v1.5.0 I managed to build and flash it to nrf52840 board without problems. However if I enable MCUboot option with 
 CONFIG_BOOTLOADER_MCUBOOT=y 
 the build fails with the following error</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 05 Mar 2021 08:29:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/72187/v1-5-0-mcuboot-build-fail" /><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297968?ContentTypeID=1</link><pubDate>Fri, 05 Mar 2021 08:29:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:779acae0-8638-4782-be4d-6f909d9dda10</guid><dc:creator>eva_c</dc:creator><description>&lt;p&gt;Ok, thank you for checking that out. I will stick with shorter folder paths for now. &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297589?ContentTypeID=1</link><pubDate>Wed, 03 Mar 2021 16:04:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7abb324-7ef4-442e-a995-05d4457e0638</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;I got in contact with some of the developer internally and got informed this is a known issue hard to do much about. See the following:&amp;nbsp;&lt;a href="http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/known_issues.html#build-system"&gt;http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/known_issues.html#build-system&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The workaround is the following:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;quot;Shorten the build folder name, e.g. from “build_nrf5340dk_nrf5340_cpuappns” to “build”, or shorten the path to the build folder in some other way.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;We are looking into how we may minimize the issue, such as using differently named build folders, not using user&amp;#39;s home as default path, etc.&lt;/div&gt;
&lt;div&gt;But all those will just be work arounds to the fundemetal problem of&amp;nbsp;Windows path length limitation.&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297425?ContentTypeID=1</link><pubDate>Wed, 03 Mar 2021 09:45:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9742d3bb-ff53-4c72-9ed7-5720df58ce78</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;Ah, okay, so you are able to get it to work if you move it close to C:/. Would it be possible to go with that as a temporary workaround? I&amp;#39;ve forwarded this issue to the developers internally. I&amp;#39;ll keep you updated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297385?ContentTypeID=1</link><pubDate>Wed, 03 Mar 2021 08:19:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:961f1bd7-0e23-47ee-a57a-63cf8dcf3e06</guid><dc:creator>eva_c</dc:creator><description>&lt;p&gt;Thank you for looking into that.&lt;br /&gt;&lt;br /&gt;I did already enable longer paths on Windows, as described in above instructions. The exact Cmake warning I get when building the project in folder with longer path is:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CMake Warning in C:/Users/Eva/ncs/v1.5.0/bootloader/mcuboot/boot/bootutil/zephyr/CMakeLists.txt:
  The object file directory

    C:/Users/Eva/XXX/build/modules/mcuboot/boot/bootutil/zephyr/CMakeFiles/..__bootloader__mcuboot__boot__bootutil__zephyr.dir/./

  has 211 characters.  The maximum full path to an object file is 250
  characters (see CMAKE_OBJECT_PATH_MAX).  Object file

    C_/Users/Eva/ncs/v1.5.0/bootloader/mcuboot/boot/bootutil/src/bootutil_public.c.obj

  cannot be safely placed under this directory.  The build may not work
  correctly.&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;which then results in an error:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;-- Generating done
-- Build files have been written to: C:/Users/Eva/XXX/build
-- west build: building application
[5/329] Performing build step for &amp;#39;mcuboot_subimage&amp;#39;
ninja: error: mkdir(modules/mcuboot/boot/bootutil/zephyr/CMakeFiles/..__bootloader__mcuboot__boot__bootutil__zephyr.dir/C_/Users/Eva/ncs/v1.5.0/bootloader/mcuboot/boot/bootutil): No such file or directory
ninja: error: mkdir(modules/mcuboot/boot/bootutil/zephyr/CMakeFiles/..__bootloader__mcuboot__boot__bootutil__zephyr.dir/C_/Users/Eva/ncs/v1.5.0/bootloader/mcuboot/boot): No such file or directoryil_public.c.obj

ninja: build stopped: .&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I did try to get around this by increasing CMAKE_OBJECT_PATH_MAX value, which successfully removes the warning, however the error stays. Non of this is a problem when building in folder closer to C:/, as mentioned.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297316?ContentTypeID=1</link><pubDate>Tue, 02 Mar 2021 21:39:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:873ef075-7b80-4b6f-bb51-c01797063655</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;&lt;span&gt;I&amp;#39;m handling another case at the moment where a customer tried to run a copied version of the Asset tracker application (same application with different name) through SES, and he encountered some issues when building the file&amp;nbsp;&lt;/span&gt;&lt;em&gt;..\ncs\v1.5.0\bootloader\mcuboot\boot\bootutil\src\bootutil_public.c.obj.d&lt;/em&gt;&lt;span&gt;, so something is going on here. Will see if I can get to the bottom of this.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297253?ContentTypeID=1</link><pubDate>Tue, 02 Mar 2021 15:09:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ee93e63-ff77-42e2-86e4-c0df9e1dcb55</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;You could also try to follow this&amp;nbsp;&lt;a href="https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/"&gt;https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297251?ContentTypeID=1</link><pubDate>Tue, 02 Mar 2021 15:04:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89f8f651-eedf-4bb0-aad7-b8d3baf855aa</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;I&amp;#39;m not sure what to do in order to reduce the path length, since you have already moved the project close to C:/. It would be nice if you could provide some steps how to reproduce it or share your project, then I could try to investigate it. I could make the case private if you would like to.&lt;/p&gt;
&lt;p&gt;I guess some changes have been made to the build system of NCS (Zephyr) v1.5.0 that&amp;#39;s causing longer path lengths.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: v1.5.0 MCUboot build fail</title><link>https://devzone.nordicsemi.com/thread/297080?ContentTypeID=1</link><pubDate>Tue, 02 Mar 2021 09:18:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:272406fd-eaff-4cdf-a839-e74dd0fb48f1</guid><dc:creator>eva_c</dc:creator><description>&lt;p&gt;I did manage to get the build working by moving project folder closer to C and manually updating Cmake to the latest version.&lt;/p&gt;
&lt;p&gt;However I still run into problems when trying to perform build command in my standard folder:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CMake Warning in C:/Users/Eva/ncs/v1.5.0/bootloader/mcuboot/boot/bootutil/zephyr/CMakeLists.txt:
  The object file directory

    C:/Users/XXX/build/modules/mcuboot/boot/bootutil/zephyr/CMakeFiles/..__bootloader__mcuboot__boot__bootutil__zephyr.dir/./  
  has 211 characters.  The maximum full path to an object file is 250
  characters (see CMAKE_OBJECT_PATH_MAX).  Object file

    C_/Users/Eva/ncs/v1.5.0/bootloader/mcuboot/boot/bootutil/src/bootutil_public.c.obj

  cannot be safely placed under this directory.  The build may not work
  correctly.&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;As far as I understand this is a Windows problem, but I did not have it with ncs 1.4.1 version. I did enable long paths on Windows with no success.&amp;nbsp; Is there anything else I can try besides moving project folders closer to C:/ ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>