From: Bob Feretich <bob.feretich@domain.hid>
To: xenomai@xenomai.org
Cc: Jeff Stutzman <rhino@domain.hid>
Subject: [Xenomai-help] Xenomai built by OpenEmbedded
Date: Wed, 24 Feb 2010 18:38:21 -0800 [thread overview]
Message-ID: <4B85E29D.2000202@domain.hid> (raw)
In-Reply-To: <4B858711.9040806@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
Sorry, I reused an old e-mail and forgot to change the subject line last
time. The subject line is more accurate on this e-mail.
How can I locate this previous report? (identified below)
I am willing to spend some time pushing Xenomai forward on this front,
but I will probably need some help. I have been involved with Linux
system building just long enough to be dangerous. Installing a co-kernel
is a new frontier for me.
Normally, when I need to attach a new module to the Angstrom kernel, I...
1. bitbake the Linux system. (Kernel source is deleted upon completion.)
2. bitbake the Angstrom kernel using the "-c compile" option, which
leaves the kernel source and intermediate files in place.
3. Build my kernel modules within the context of the kernel.
My theory is that the below sequence may work for Xenomai...
1. bitbake the Linux system. (Kernel source is deleted upon completion.)
2. bitbake the Angstrom kernel using the bitbake "-c compile" option,
which leaves the kernel source and intermediate files in place.
3. Apply the appropriate Adios kernel patches.
4. Rebuild the Angstrom kernel using the "-c compile" option, which
should use the patched kernel source.
5. Add the Xenomai sub-tree to the root file system.
6. Build my modules as before.
Does this make sense?
Regards,
Bob Feretich
On 2/24/2010 12:07 PM, Gilles Chanteperdrix wrote:
> Bob Feretich wrote:
>
>> Lately I have been using the OpenEmbedded bitbake tool to build my Linux
>> systems (Angstrom for BeagleBoard based). Has anyone created a recipe
>> set to build Xenomai under OpenEmbedded?
>>
>> What I really want to do is install Xenomai into the BeagleBoard
>> Angstrom kernel.
>>
>
> Yes, recently someone reported using this method. However, he had issues
> with -Wl,--as-needed which we did not elucidate completely.
>
>> Regards,
>> Bob
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help
>>
>>
[-- Attachment #2: Type: text/html, Size: 2801 bytes --]
next prev parent reply other threads:[~2010-02-25 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 18:07 [Xenomai-help] Interpreting the ksrc/arch/arm/patches directory Bob Feretich
2010-02-24 20:07 ` Gilles Chanteperdrix
2010-02-25 2:38 ` Bob Feretich [this message]
2010-02-25 7:09 ` [Xenomai-help] Xenomai built by OpenEmbedded Stefan Kisdaroczi
2010-02-25 7:42 ` Gilles Chanteperdrix
2010-02-25 9:27 ` [Xenomai-help] OpenEmbedded (bitbake) recipes for Xenomai? Bob Feretich
2010-02-25 18:10 ` Felipe Brandão Cavalcanti
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=4B85E29D.2000202@domain.hid \
--to=bob.feretich@domain.hid \
--cc=rhino@domain.hid \
--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.