From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Daniel Lazzari <dlazzari@leapfrog.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Custom tasks not running when dependency changes version
Date: Fri, 03 May 2013 16:26:00 +0100 [thread overview]
Message-ID: <1367594760.5379.157.camel@ted> (raw)
In-Reply-To: <E7A9054A5ACABE48B0E540E46E862B0FE6C9AF83@NAEMMAIL01.na.leapfrog.com>
On Sun, 2013-04-28 at 01:14 +0000, Daniel Lazzari wrote:
> I've got a weird issue that I just can't seem to figure out and need some help on. In our custom layer we have a bbclass that has 2 custom tasks, like so:
>
> addtask complete_metadata after do_package before do_package_write
> addtask create_other_package after do_package_write before do_build
>
> Now this is inherited by a recipe B which depends on recipe A. If I build a rootfs image, then change the version (PV) on recipe A, then build the rootfs image again, recipe A rebuilds, then recipe B rebuilds, but it rebuilds without running my custom tasks. There's probably some task flag that I need to set to make this work, but I can't figure out what it is. Any help is appreciated, as always.
>
> BTW, I'm all the way back on the denzil branch in case that matters.
We have recently found a cache issue in bitbake with regard to addtask
handling. The fix is now in master:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=6db202532122b213ae6cfce9a49ac9fad2db20f5
You can workaround this by removing tmp/cache/ to ensure bitbake
correctly reparses things when it should. It may be the problem you're
seeing, it may not but its worth a try...
Cheers,
Richard
next prev parent reply other threads:[~2013-05-03 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 1:14 Custom tasks not running when dependency changes version Daniel Lazzari
2013-05-03 15:26 ` Richard Purdie [this message]
2013-05-03 22:57 ` Daniel Lazzari
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=1367594760.5379.157.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dlazzari@leapfrog.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 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.