From: ChenQi <Qi.Chen@windriver.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image.bbclass: depends on virtual/kernel
Date: Mon, 25 Nov 2013 20:09:05 +0800 [thread overview]
Message-ID: <52933DE1.3050202@windriver.com> (raw)
In-Reply-To: <CAAQYJAsmtSLkxnukhv=Guj5cJPhy23UixnZ-aaWB8CjsgbAaQQ@mail.gmail.com>
On 11/23/2013 06:32 AM, Andrea Adami wrote:
> On Fri, Nov 22, 2013 at 8:58 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Fri, Nov 22, 2013 at 3:39 AM, <Qi.Chen@windriver.com> wrote:
>>> From: Chen Qi <Qi.Chen@windriver.com>
>>>
>>> Add 'virtual/kernel' to DEPENDS in image.bbclass so that the kernel
>>> can get built by default. Otherwise, the kernel will not get built
>>> unless it's required by other packages like v86d. As a result, if
>>> we build 'core-image-minimal' for qemumips, the kernel is not built,
>>> and we have 'bitbake linux-yocto' before we can use runqemu to start
>>> the target.
>>>
>>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> If I have a board without modules there's no need to have the depends.
>> Why you need this?
>>
> The first quenstion in my mind when I read the post:
>
> Odd...wasn't core-image-minimal purposedly lean, mutilated and without
> kernel modules ?
> (Not that really 'used' it, just booted 'cause was small and could
> always fit on nand/nor)
What I want to do here is to trigger building of kernel when building
out an image. I'm not proposing to make all images have kernel -modules
installed.
> It has always been like this: if one needs the kernel and the modules
> can add that in his machine.conf.
Previously, the kernel is built out by default because
packagegroup-core-boot has a dependency on it. Now the dependency is gone.
I'm not talking about installing kernel modules onto images.
Best Regards,
Chen Qi
> For more demanding tasks, the next logical step is core-image-base.
>
>
> My 2 cents
>
> Andrea
>
>
>
>> --
>> Otavio Salvador O.S. Systems
>> http://www.ossystems.com.br http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-11-25 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 5:39 [PATCH 0/1] image.bbclass: depends on virtual/kernel Qi.Chen
2013-11-22 5:39 ` [PATCH 1/1] " Qi.Chen
2013-11-22 11:38 ` Martin Jansa
2013-11-22 11:41 ` Phil Blundell
2013-11-22 12:06 ` Richard Purdie
2013-11-22 19:58 ` Otavio Salvador
2013-11-22 22:32 ` Andrea Adami
2013-11-25 12:09 ` ChenQi [this message]
2013-11-25 12:28 ` Otavio Salvador
2013-11-25 12:57 ` Richard Purdie
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=52933DE1.3050202@windriver.com \
--to=qi.chen@windriver.com \
--cc=andrea.adami@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox