From: Gary Thomas <gary@mlbassoc.com>
To: Tom Rini <tom_rini@mentor.com>
Cc: poky@yoctoproject.org
Subject: Re: Customizing kernels
Date: Wed, 27 Jul 2011 14:08:28 -0600 [thread overview]
Message-ID: <4E30703C.6060708@mlbassoc.com> (raw)
In-Reply-To: <4E306DF5.40908@mentor.com>
On 2011-07-27 13:58, Tom Rini wrote:
> On 07/27/2011 10:25 AM, Gary Thomas wrote:
>> To run a customized kernel configuration, I've been doing this:
>> % bitbake virtual/kernel
>> % bitbake virtual/kernel -c menuconfig
>> % bitbake virtual/kernel -c compile -f
>> % bitbake virtual/kernel
>>
>> Is there some way that the kernel recipes (probably kernel.bbclass)
>> could mark the compile state as invalid so that the '-c compile -f'
>> step is no longer needed (implied)?
>
> What's the reason around the first bitbake? I know with pstage you
> needed to do that for an empty TMPDIR to populate out everything else,
> but sstate shouldn't have that weakness. It should just be:
> $ bitbake virtual/kernel -c menuconfig
> $ bitbake virtual/kernel
>
> And get populating from sstate correct.
>
The first step was just to get started, e.g. from scratch (no sstate, etc)
The situation I'm really talking about is when you've already built the
whole thing (presumably a full image, etc) and then want to change some
kernel option, e.g. add a non-module driver and not rebuild the kernel
from scratch, just recompile the required bits. In this case, if you
just run the two steps you quote, nothing happens during the second
step because bitbake thinks that the whole recipe is complete. Once
you run '-c compile -f', it will rerun the compile and that invalidates
the steps that follow in the recipe so they all run as well.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-07-27 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 17:25 Customizing kernels Gary Thomas
2011-07-27 19:58 ` Tom Rini
2011-07-27 20:08 ` Gary Thomas [this message]
2011-07-27 20:17 ` Tom Rini
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=4E30703C.6060708@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=tom_rini@mentor.com \
/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.