All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Maksym Parkachov <lazy.gopher@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai on Yocto/Openembedded
Date: Sat, 13 Oct 2012 11:57:34 +0200	[thread overview]
Message-ID: <50793B0E.5020002@xenomai.org> (raw)
In-Reply-To: <CAHQk_AR+n7pq==TSTz5JwVRhg=jOKMXKniGrgdVTVTea5=aq1Q@mail.gmail.com>

On 10/13/2012 11:13 AM, Maksym Parkachov wrote:

> Hi Flavio,
> 
>> Has anybody tried to create a package for Xenomai for Yocto or Openembedded?
> 
> I have a client side package at my layer, you could check it at:
> 
> http://github.com/veter-team/veterlayer/tree/master/recipes/xenomai
> 
> It's pretty strait forward. Kernel is different story, I've just made
> a patch to customized kernel:
> 
> http://github.com/veter-team/veterlayer/tree/master/recipes/linux
> 
> Hope this helps,
> Maksym.
> http://veter-project.blogspot.com


Adding I-pipe and Xenomai as a single patch to the kernel does not seem
the way to go.

I would rather have the linux kernel building rules call
prepare-kernel.sh to apply the I-pipe patch and setup xenomai links to
the xenomai package source directory. It is not really hard, and it
makes things way easier to maintain.

-- 
                                                                Gilles.


  reply	other threads:[~2012-10-13  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 23:46 [Xenomai] Xenomai on Yocto/Openembedded Flavio Castro Alves Filho
2012-10-13  9:13 ` Maksym Parkachov
2012-10-13  9:57   ` Gilles Chanteperdrix [this message]
2012-10-13 10:02     ` Maksym Parkachov
2012-10-13 10:04       ` Gilles Chanteperdrix
2012-10-14 18:16         ` Flavio Castro Alves Filho
2012-10-13 12:38 ` Marco Cavallini
2012-10-13 12:50   ` Gilles Chanteperdrix
2012-10-15  6:31     ` Marco Cavallini
2012-10-15  7:55 ` Lukasz Zemla

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=50793B0E.5020002@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=lazy.gopher@gmail.com \
    --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.