From: Mike Looijmans <mike.looijmans@topic.nl>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: How to move a recipe to another directory without invalidating its sstate-cache?
Date: Wed, 16 Dec 2015 10:38:18 +0100 [thread overview]
Message-ID: <5671310A.1000000@topic.nl> (raw)
I renamed "recipes-some/foo/bar.bb" to "recipes-some/buzz/bar.bb"
Rebuilding bar and its dependencies will take about 16 hours. So I don't want
to trigger a rebuild.
running "bitbake -S printdiff bar" only reveils this:
The differences between the current build and any cached tasks start at the
following tasks:
.../recipes-some/buzz/bar.bb, do_configure
NOTE: Reparsing files to collect dependency data
Writing locked sigs to .../build/locked-sigs.inc
Task bar:do_configure couldn't be used from the cache because:
We need hash 52209720c011f1f165a0bbb042d9b12b, closest matching task was
25b3674b7a678faf1ac623bf0d836bb9
runtaskdeps changed from [..., 'foobar.bb.do_patch'] to
['buzzbar.bb.do_patch', ...]
So apparently some mysterious variable appears to include the location of the
recipe. I would not have expected the "foo" and "buzz" words to be present
anywhere. The recipe itself doesn't use or need a configure step.
But my primary question is now: What variable can I set to prevent a rebuild?
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next reply other threads:[~2015-12-16 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 9:38 Mike Looijmans [this message]
2015-12-16 12:35 ` How to move a recipe to another directory without invalidating its sstate-cache? Richard Purdie
2015-12-16 13:18 ` Mike Looijmans
2015-12-16 13:26 ` Mike Looijmans
2015-12-16 13:33 ` Richard Purdie
2015-12-17 6:24 ` Mike Looijmans
2015-12-17 12:47 ` Mike Looijmans
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=5671310A.1000000@topic.nl \
--to=mike.looijmans@topic.nl \
--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.