Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
>  > Known limitations are:
>  > (...)
>  > - for an unknown reason, xenomai modules are built every time
>  > is run ;
> The reason for this limitation is that remove
> directories before re-creating them and before creating symbolic links.

At this chance, something from my private whish list: :)

"" or so, i.e. turning the kernel in its original
vanilla state again.

This is helpful when applying/reversing third-party kernel patches which
also touch the modified Makefiles. I think on some 2.4 kernel, even
reverting ipipe collides with the xeno-preparation.

> The previous patch was also incorrect when trying to cross-compile the
> Linux kernel or building it for ppc. The attached patch fixes these
> issues.

Regarding your general idea, I'm just trying to imagine the new build
process: you prepare and build the kernel + the userspace stuff again in
one step?. But you still have to configure both parts separately.

The question for me is now if this simplifies the situation expecially
for beginners. So far, the separation was clearly visible, now it /may/
become blurred (but I'm not a beginner...).

Can you provide a rough comparision of the workflows? Sorry, but I'm too
lazy, I mean busy to give it a try.


Attachment: signature.asc
Description: OpenPGP digital signature

Xenomai-core mailing list

Reply via email to