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 20:58:46 +0100	[thread overview]
Message-ID: <43C01D76.3090808@domain.hid> (raw)
In-Reply-To: <17344.5951.309397.423794@domain.hid>

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

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>  > > 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.
> 
> configure --enable-linux-build
> make xconfig
> make install
> 

I'm starting to like this!

> If you already have a .config file, the "make xconfig" step becomes
> optional.
> 
> Note that the --enable-linux-build flag is optional too.
> 
> The simplification is mainly for developping xenomai itself, not for its
> users. Because with the current scheme, after some modifications, you
> have to recompile and reinstall both the kernel-space modules and
> user-space libraries.
> 
> If you let configure select the proper adeos patch, you are warned when
> the adeos patch changed in the source directory (after an svn update,
> for example), and just have to type: 
> rm linux/.xenomai-prepared (Ok, this step is a bit awkward, we may find
>                             something better)
> make install
> 
> And a new kernel will be built and installed, using the new adeos patch
> and the same .config.
> 

Hmm, what about this: Instead of leaving some (probably empty)
xenomai-prepared in the kernel tree, better create an xenomai-uninstall
script in the same place. It a) can serve as an indication for a
prepared kernel and b) can be used to upgrade that tree by first running
it and then applying the usual steps on the kernel again.

I often forget to save my old adeos patch before updating the xenomai
tree, thus I will then have to download the old patch again,
reverse-apply it, and can finally run the prepare script for the update.
Automating this would be REALLY, REALLY GREAT!

Jan

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

  reply	other threads:[~2006-01-07 19:58 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
2006-01-07 19:32     ` Gilles Chanteperdrix
2006-01-07 19:58       ` Jan Kiszka [this message]
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=43C01D76.3090808@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.