**** BEGIN LOGGING AT Sun Feb 16 02:59:57 2020
Feb 16 17:09:10 <BlastuR> Hi! I'm trying write a recipe (lets call it A.bb) that packages a program that requires some custom kernel headers (UAPI) that are not in mainline kernel. Because they are not in mainline, they don't get installed by openembedded linux-libc-headers.bb. Reading linux-libc-headers.inc, it explicitly says not to modify the recipe to use a custom kernel but instead write another recipe that installs the
Feb 16 17:09:12 <BlastuR> headers so they can be in another package sysroot. I suppose this will work, so I tried appending header installation to my kernel recipe and then let A.bb DEPENDS on the kernel so the headers from the kernel would end up in A.bb's "recipe-sysroot". It didn't. And I don't understand why! In the kernel recipe, I'm installing the headers into ${D}${includedir} and from what I understand reading
Feb 16 17:09:14 <BlastuR> staging.bbclass, any files installed into the SYSROOT_DIRS (which includes ${includedir}) will end up in the recipe-sysroot. How can I debug this issue? My kernel recipe is based on linux-yocto.inc which in turn inherits kernel.bbclass. I noticed there is some funky rewrite of PACKAGES and FILES in there. Could this be related? If I just look at my recipes ${WORKDIR}/package, the headers end up in the
Feb 16 17:09:16 <BlastuR> correct folders. They just don't end up in the sysroot of my other package. Any ideas what I'm doing wrong?
Feb 16 18:18:55 <BlastuR> However, when I create a simple test recipe B.bb which only installs a file into ${D}${includedir} and put ${includedir} into its FILES, and then let A.bb DEPENDs on that, the header file correctly gets placed into the sysroot of A. I highly suspect the issue is with linux-yocto.inc somehow messing up the sysroot of my recipe somehow
Feb 16 19:41:34 <Jin^eLD> n
Feb 16 19:44:14 <Jin^eLD> tlwoerner: I submitted a patch to have the fw_env.config be automatically generated for the libubootenv package, I hope it's useful, did cost me some time to figure that out yesterday
Feb 16 19:44:30 <Jin^eLD> but i was not sure about other rockchips so I only added it for rk3288
Feb 16 19:44:46 <Jin^eLD> although u-boot only ifdefs on "ROCKCHIP" so its probably valid for all
**** ENDING LOGGING AT Mon Feb 17 02:59:57 2020