From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: rm_work not cleaning up when doing "-c populate_sdk"
Date: Mon, 5 May 2014 16:10:56 +0800 [thread overview]
Message-ID: <53674790.7060405@windriver.com> (raw)
In-Reply-To: <CAMKF1soHJS21Or1b=hByJrRCV5qL343NjkNXXUx__fgnVaKsfw@mail.gmail.com>
I've sent out a patch to the list, trying to fix this problem.
Please take a look at it if convenient.
Best Regards,
Chen Qi
On 05/05/2014 10:21 AM, Khem Raj wrote:
> On Sun, May 4, 2014 at 1:04 PM, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>> Hello,
>>
>> I'm using the rm_work class in my setup, and I noticed that the work
>> directories for all my nativesdk-* packages we're not being cleaned up.
>>
>> I do "bitbake -c populate_sdk my-image" to create the SDK.
>>
>> From what I can tell by looking at rm_work.class, the rm_work task is
>> appended at the end, but for some reason rm_work is not executed.
>>
>> If I do "bitbake nativesdk-<somepackage>", rm_work is indeed executed.
>>
>> Would it be possible to hook in rm_work in the populate_sdk case as well ?
>> Or is there another way of executing rm_work for all packages ?
>>
> rm_work is run before BB_DEFAULT_TASK which is set to 'do_build' in bitbake.conf
>
> populate_sdk is added to be executed before do_build as well but there
> is no dependency
> of rm_work on populate_sdk thats the issue here they are independent.
>
>
>
>> -- Jacob
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
prev parent reply other threads:[~2014-05-05 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 20:04 rm_work not cleaning up when doing "-c populate_sdk" Jacob Kroon
2014-05-05 2:21 ` Khem Raj
2014-05-05 8:10 ` ChenQi [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=53674790.7060405@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox