offsets.h No such file or directory

[Mathi]

Hi, 

We have been using SDK version 2.1.1 and currently are in the process of migrating to SDK version 2.5.0.

Would be helpful to get some hint regarding what conditions can lead to the following error when building our application.

In file included from C:\ncs\v2.5.0\zephyr\include\zephyr\app_memory\app_memdomain.h:9,
from C:\ncs\v2.5.0\zephyr\include\zephyr\rtio\rtio.h:31,
from C:\ncs\v2.5.0\zephyr\include\zephyr\drivers\i2c.h:28,
from <our application.h>...
C:\ncs\v2.5.0\zephyr\include\zephyr\linker\linker-defs.h:26:10: fatal error: offsets.h: No such file or directory
26 | #include <offsets.h>
| ^~~~~~~~~~~

Thanks,

Mathi.

[robertp]

I also have this issue and I have created a minimal reproducible example. In my case, moving the i2c.h file to the .cpp file does not work. Here's a github link to my example. robertpaananen/mre_bug_offsets_h: MRE for offsets.h bug (github.com)

[Sigurd Hellesvik]

Thanks for the example!
I am able to reproduce it with your project, but only once per build per board, so that is quite odd.
Unfortunately I have not been able to find the root for this yet.
So I have asked our developers, some of which are contributors to Zephyr as well, so I hope to learn more from them. I also will ask around to some of my colleagues in technical support to see if they have any ideas.

[robertp]

Thanks for your time. The build folder needs to be deleted between builds for this bug to appear again, so something weird is definitely going on here. 

[Bogdan Marinescu]

It's not that weird. offsets.h is generated by the Zephyr build system and once generated it (generally) doesn't change between builds, this is why the bug is only reproducible with a clean build. The weird part is what changed in the Zephyr/NCS build system to generate this file at a different build stage.