[oe] Added header file to linux kernel - how to export
Aeschbacher, Fabrice
Fabrice.Aeschbacher at siemens.com
Tue Jul 19 18:14:14 UTC 2011
Hi,
Your could put something like this:
do_stage_append() {
cp ${S}/my_ioctl.h ${STAGING_KERNEL_DIR}/include/linux
}
in your recipes/linux<xxx>.bb
With kind regards,
Fabrice
> -----Ursprüngliche Nachricht-----
> Von: openembedded-devel-bounces at lists.openembedded.org
> [mailto:openembedded-devel-bounces at lists.openembedded.org] Im
> Auftrag von Mats Kärrman
> Gesendet: Dienstag, 19. Juli 2011 15:57
> An: openembedded-devel at lists.openembedded.org
> Betreff: [oe] Added header file to linux kernel - how to export
>
> Hi,
>
> I have made a patch to the linux kernel, involving adding
> some ioctl's. Relevant definitions are in a .h file. Now I
> need to access this .h file from another recipe (that builds
> a utility using those ioctl's) but the headers in
> sysroots/xxx-linux/usr/include are put there (by
> linux-libc-headers?) long before the target Linux kernel is
> patched and built.
>
> I'm thinking about adding a do_install_append to the linux
> recipe but that doesn't feel right. Neither does adding a
> path from the util recipe build to the work folder of linux
> kernel. Third alternative would be to build the driver as an
> LKM but I really like to have it built into the kernel...
>
> If any of you have some good advice here I would be very happy!
>
> Best Regards,
> Mats
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
More information about the Openembedded-devel
mailing list