<?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>Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91577/code-generated-using-mesh-results-in-embedded-file-paths</link><description>For some reason when we build a MESH enabled app we are getting a resulting hex file that includes complete file paths names. This is not occurring in our builds that do not use MESH. Is this a known issue or is there a know culprit? 
 
 Thank you</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 12 Sep 2022 12:30:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91577/code-generated-using-mesh-results-in-embedded-file-paths" /><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/385736?ContentTypeID=1</link><pubDate>Mon, 12 Sep 2022 12:30:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e938dfa4-a736-4a69-a53d-3694796dcf3e</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;nRF5 SDK for Mesh is very different from nRF Connect SDK, yes. For new products we recommend nRF Connect SDK, see our &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement"&gt;nRF Connect SDK and nRF5 SDK statement&lt;/a&gt;. The solution I provided earlier is for nRF Connect SDK.&lt;/p&gt;
&lt;p&gt;In nRF5 SDK, file and line numbers are printed from the assert handler, but that should be solved by doing a Release build. Apart from that, you might have to change the mesh logging manually here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/a165eece1b743bc68ef396bf03ba389a0bac6f11/mesh/core/include/log.h#L288"&gt;https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/a165eece1b743bc68ef396bf03ba389a0bac6f11/mesh/core/include/log.h#L288&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/385383?ContentTypeID=1</link><pubDate>Thu, 08 Sep 2022 19:08:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:becf4f9b-c38f-4b2d-b043-1c1f294bb28a</guid><dc:creator>CanuckAbroad</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Thank you for the reply,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am unable to find the file prj.conf, and when I search for references to it here on this website I find it referred to in the nRF Connect SDK, and more specifically for Zephyr.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;also, this file does not seem to exist in the Segger directories, my project directories or the MESH SDK 5.0 directories.&lt;/p&gt;
&lt;p&gt;Is there an alternate solution that will work for the situation I am using?&lt;/p&gt;
&lt;p&gt;- Segger embedded studio&lt;/p&gt;
&lt;p&gt;- BLE Mesh coexistence&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/385322?ContentTypeID=1</link><pubDate>Thu, 08 Sep 2022 13:35:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3713cdf7-2b84-4ecb-97c2-c48710935aed</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Add to the file prj.conf the following line:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;CONFIG_ASSERT_NO_FILE_INFO=y&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/385130?ContentTypeID=1</link><pubDate>Thu, 08 Sep 2022 00:44:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:171b0a36-2bcf-42bb-8a0d-deb215075380</guid><dc:creator>CanuckAbroad</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Where is this option set exactly? Please note I am using Segger Embedded Studio.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;
&lt;p&gt;Warren&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/384827?ContentTypeID=1</link><pubDate>Tue, 06 Sep 2022 14:00:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bbcd3387-ed65-4832-b181-5f01ed28333d</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Enabling the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_ASSERT_NO_FILE_INFO"&gt;ASSERT_NO_FILE_INFO&lt;/a&gt; option removes file names and file paths from assert error messages, which seems to be what you have found in your binaries.&lt;/p&gt;
&lt;p&gt;I did a test with the mesh chat example, and after setting that option I no longer find any file paths in the resulting binaries.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/384438?ContentTypeID=1</link><pubDate>Sat, 03 Sep 2022 00:38:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:be38b9f2-72a2-46f7-89ed-f2c98cee4a24</guid><dc:creator>CanuckAbroad</dc:creator><description>&lt;p&gt;Yes, this is what we are encountering. Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Code generated using MESH results in embedded file paths.</title><link>https://devzone.nordicsemi.com/thread/384420?ContentTypeID=1</link><pubDate>Fri, 02 Sep 2022 12:59:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dda3c6e3-9ee3-4ccb-9769-ea1fde646f7c</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Building the mesh chat example of the nRF Connect SDK, I do find some paths in the resulting binary, that are relative to the SDK root folder. They seem to stem from log messages. Is that what you see as well?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>