All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [rfc] Building Linux kernel in Xenomai tree.
Date: Sat, 07 Jan 2006 19:38:15 +0100	[thread overview]
Message-ID: <43C00A97.4020404@domain.hid> (raw)
In-Reply-To: <17344.665.154004.811426@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

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

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

"unprepare-kernel.sh" 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.

Jan

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2006-01-07 18:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 11:30 [Xenomai-core] [rfc] Building Linux kernel in Xenomai tree Gilles Chanteperdrix
2006-01-07 18:04 ` Gilles Chanteperdrix
2006-01-07 18:38   ` Jan Kiszka [this message]
2006-01-07 19:32     ` Gilles Chanteperdrix
2006-01-07 19:58       ` Jan Kiszka
2006-01-07 21:24         ` Gilles Chanteperdrix
2006-01-08 12:08 ` Philippe Gerum
2006-01-08 13:08   ` Gilles Chanteperdrix
2006-01-08 14:17     ` Philippe Gerum
2006-01-08 16:55       ` Gilles Chanteperdrix
2006-01-08 19:23         ` Philippe Gerum
2006-01-08 20:22           ` Gilles Chanteperdrix
2006-01-08 21:39             ` Philippe Gerum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43C00A97.4020404@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.