[OE-core] bitbake -c clean <package> fails

[Ulf Samuelsson]

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 at lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core