From: Ulf Samuelsson <ulf@emagii.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake -c clean <package> fails
Date: Wed, 08 Feb 2012 10:21:24 +0100 [thread overview]
Message-ID: <4F323E94.2040307@emagii.com> (raw)
In-Reply-To: <20120207224006.GA13125@sakrah.homelinux.org>
On 2012-02-07 23:40, Khem Raj wrote:
>>> Clean it's just a "clean". As in "make clean". So after a clean
>>> you will typically have configure, compile etc.
>>> "cleanall" = remove unpacked + remove source. So after a clean you
>>> will tipically have fetch.
>> I have tried clean, cleansstate and cleanall.
>> All of them remove the source directory.
> if you are talking about ${S} then yes but relevant content in ${DL_DIR} are only removed
> with cleanall
>
Yes, when I work on the kernel, I do not want to restart from unpack.
I would like to edit the existing ${S}and then restart a compile.
Once the compile succeeds, I want to deploy.
Once the kernel does what it is supposed to, I generate a patch
which is then added to the recipe.
At that time, I want to cleansstate and rebuild/retest.
To come around this problem right now, my kernel recipe generates a script
in ${S}, which will compile the kernel image and then copies it directly
to my tftp directory.
>> If I try to use XorA's method of testing out the kernel
>> http://www.xora.org.uk/2009/12/10/openembeddedangstrom-kernel-workflow/
>> then it fails since a recompile of the source will fail to update
>> dependencies.
>> If i bitbake -c compile virtual/kernel -f a
>> and then
>> bitbake virtual/kernel
>> then the previous build will be used.
>>
>> Is it at all possible now to recompile, without having to clean out
>> everything,
>> and start from scratch?
>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-02-08 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 13:56 bitbake -c clean <package> fails Ulf Samuelsson
2012-01-29 14:04 ` Koen Kooi
2012-01-29 17:35 ` Khem Raj
2012-01-30 9:48 ` Andrei Gherzan
2012-02-07 11:45 ` Ulf Samuelsson
2012-02-07 22:40 ` Khem Raj
2012-02-08 9:21 ` Ulf Samuelsson [this message]
2012-02-08 9:54 ` Andrei Gherzan
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=4F323E94.2040307@emagii.com \
--to=ulf@emagii.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.