Re: linux-libc-headers - how to handle for older kernels?

Mikko Rapeli


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
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...
This is the problem I see with multiple BSPs. In the end for every one of them
the best solution is to fork linux-libc-headers.

Adding custom recipes to export headers for every BSP kernel is not scaling so well.

Sharing the BSPs and hacks around them would be nice but they are not public sadly :(



Join to automatically receive all group messages.