From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Using openembedded with externally built kernel
Date: Thu, 13 Mar 2014 18:36:18 +0100 [thread overview]
Message-ID: <5321EC92.6070304@balister.org> (raw)
In-Reply-To: <CAMCfZKHx9PnjzqfJSXUj-ZOvG2b_PPWnAWdD6jqS+Npx3xsX8A@mail.gmail.com>
On 03/13/2014 12:56 PM, Diego Sueiro wrote:
> On Wed, Mar 12, 2014 at 10:48 AM, Carlos Rafael Giani <dv@pseudoterminal.org
>> wrote:
>
>> I have a platform with a very barebones BSP that builds and patches a 2.6
>> kernel using a whole lot of shell scripts and patch files.
>> Integrating this build process into a .bb file is too complicated at the
>> moment.
>>
>> Since cross compiling all packages I need is a nightmare to do manually, I
>> wonder if I can get OE to use the prebuilt kernel along with
>> its kernel modules and headers instead of trying to build a new kernel.
>> Ideally, I would just tell it where the kernel headers are, where
>> the uImage is, and where the modules are. I imagine this as some kind of
>> kernel .bb file setting things up to not actually build anything.
>>
>> My question is: is this possible? All I could find was about external
>> toolchains and external kernel modules.
>>
>
> I believe that you have to wright your own recipe with custom do_compile,
> do_install etc functions.
Write a recipe that "installs" the pre-built kernel and a tarball of
modules and commit the binary kernel and modules into the bsp layer.
Yeah, this is hacky, but does give you some repeatibility.
Philip
>
>
>
> Abraços,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/
>
prev parent reply other threads:[~2014-03-13 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 13:48 Using openembedded with externally built kernel Carlos Rafael Giani
2014-03-13 11:56 ` Diego Sueiro
2014-03-13 17:36 ` Philip Balister [this message]
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=5321EC92.6070304@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.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.