Code generated using MESH results in embedded file paths.

[CanuckAbroad]

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

[tesc]

Hi,

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?

Regards,
Terje

[CanuckAbroad]

Yes, this is what we are encountering. Thank you

[tesc]

Hi,

Enabling the ASSERT_NO_FILE_INFO option removes file names and file paths from assert error messages, which seems to be what you have found in your binaries.

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.

Regards,
Terje

[CanuckAbroad]

Hello,

Where is this option set exactly? Please note I am using Segger Embedded Studio.

Thank you

Warren

[tesc]

Hi,

Add to the file prj.conf the following line:

CONFIG_ASSERT_NO_FILE_INFO=y

Regards,
Terje