On Mon, Dec 02, 2019 at 04:01:41PM +0200, Adrian Bunk wrote:
On Mon, Dec 02, 2019 at 09:33:33AM +0000, Mikko Rapeli wrote:
...The fork can be a .bbappend with a patch adding the required
On Mon, Dec 02, 2019 at 09:28:03AM +0000, Mike Looijmans wrote:
One solution I can think of is to put the header into it's own This is the problem I see with multiple BSPs. In the end for every one of them
recipe/repository and then refer to it like any other library would. Refer to
that recipe from the module (or kernel) recipe that needs it. This way you
have your header in a single maintainable location and dependencies properly
taken care of.
If that's not something you could live with, share your recipes, since vague
problem descriptions will only get you vague solutions...
the best solution is to fork linux-libc-headers.
definitions to linux-libc-headers.
Yes, this is what I meant. Basically just adjust the SRC_URI and possibly PV
through a linux-libc-headers_%.bbappend in product or BSP specific meta layer.