Hi Mikko, Do you have an example on how you do that ? Do you bbapend the linux-libc-headers recipe file ? I have an application that uses dmabuf heap that potentially extends across multiple BSP's as its BSP agnostic. I don't want to be patching individual BSP recipes and generating headers. The issue I am facing is due to backporting the patch from 5.6 to 5.4 so the required header isn't a part of the linux-libc-headers.bb recipe. Best would have been a virtual/kernel-keaders target that applications that require BSP headers would add to their recipe DEPENDS. Why is this not a solved issue by yocto project ? Why do individual BSP's need to deal with this differently when the header install mechanism (make headers_install) is the same irrespective of the type of BSP ?
On Tue, Feb 23, 2021 at 5:18 AM <[email protected]> wrote: > > Hi, > > I know it's not the best or recommended approach, but I find it > hard to avoid merging linux-libc-headers recipe with the actual > kernel recipe that a distro is using. At least a static copy > of some version of uapi headers from that kernel can be used > instead of the poky side linux-libc-headers. This helps to get > the actual BSP SW delivery headers into userspace, SDK etc. > > Cheers, > > -Mikko -- Regards, Karthik Poduval
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52454): https://lists.yoctoproject.org/g/yocto/message/52454 Mute This Topic: https://lists.yoctoproject.org/mt/80841186/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
