<p dir="ltr">You should write a bbappend for linux libc headers recipe and apply the patch to kernel and expose is that way. But before doing that I would suggest that you work with driver owner to submit their header to kernel. Since you can get into conflicts in future.</p>
<div class="gmail_quote">On Apr 1, 2016 8:38 PM, "Andre McCurdy" <<a href="mailto:armccurdy@gmail.com">armccurdy@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Say I have a kernel driver with a user space API (simple struct and<br>
ioctl definitions) defined in a header file which is part of my<br>
machine specific kernel. The header file is not found in the upstream<br>
kernel, so doesn't clash with anything in linux-libc-headers.<br>
<br>
Is it OK to use something like the following in my kernel recipe?<br>
<br>
sysroot_stage_all_append () {<br>
install -d ${SYSROOT_DESTDIR}/${includedir}/linux<br>
install -m644 ${S}/include/linux/foo.h<br>
${SYSROOT_DESTDIR}/${includedir}/linux/<br>
}<br>
<br>
I've tested it and everything seems to work fine, but I'm wondering if<br>
bypassing do_install like that is going to cause problems somehow?<br>
--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div>