On 2017-12-19 19:49, Steve Pavao wrote:
> Hi Lowell,
>
> Thanks for that tip. That’s what I was thinking I might need to do.
>
> I guess the solution in Yocto terms is to rework my I-PIPE patch recipe to
> not directly apply the I-PIPE patch, but rather to call prepare-kernel.sh and
> allow it to apply the patch, plus do the other things it needs to do. I
> guess that should happen in a do_configure() {} block.
Actually, I would move the kernel patching out of the xenomai recipe and
rather have one recipe for the userspace packages and a
xenomai-kernel.inc which appends the kernel preparation task with the
prepare-kernel.sh invocation. It would also bring in (once again) the
xenomai sources so that its kernel elements get pulled into the kernel
build. In your kernel recipe, you would simply include that file.
This way, the kernel could come from various sources, including
git.xenomai.org/ipipe.git, and just needs to have the I-pipe patch
already applied, either in it git source or by adding a corresponding
patch to the custom kernel recipe.
This seems similar to how ELDK modeled this:
http://git.denx.de/?p=eldk.git;a=tree;f=meta-eldk/recipes-kernel/xenomai;h=bf965c6d2fa5132413b498161c90f337be8fb174;hb=refs/heads/5.8-eldk
That is outdated now, unfortunately. Do you plan to publish your layer
afterwards? I suppose some people would be happy about a meta-xenomai
with support for Xenomai 3.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
_______________________________________________
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
