From: Mike Looijmans <mike.looijmans@topic.nl>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: OE-core] How do I find out why are packages being rebuilt?
Date: Mon, 18 Feb 2013 12:04:12 +0100 [thread overview]
Message-ID: <51220AAC.8080201@topic.nl> (raw)
In-Reply-To: <20130210195919.GA3300@jama>
I'm still having trouble with packages being needlessly rebuilt over and
over. The worst of all it qt4-embedded, it takes about an hour to build.
This is wasting a LOT of time.
The classic OE never rebuilt a package until its version changed.
How and why the current oe-core decides to rebuild package is a complete
mystery to me, and the outdated documentation on the oe wiki isn't any
help in that respect either.
Can anyone explain how I can gain some insight into the "trigger" that
causes a certain package to be rebuilt?
next prev parent reply other threads:[~2013-02-18 11:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:29 Multiple MACHINE building is broken in OE-core? Mike Looijmans
2013-01-29 9:40 ` Martin Jansa
2013-01-29 10:21 ` Mike Looijmans
2013-01-29 10:48 ` Burton, Ross
[not found] ` <510B73EB.8060907@topic.nl>
[not found] ` <CAJTo0LbkOMXqZkHd-JAcNKxiOmXTy+TXPEEJ-CkPc1Jx3Ujekg@mail.gmail.com>
2013-02-01 12:59 ` Mike Looijmans
2013-02-01 14:00 ` Burton, Ross
2013-02-09 19:39 ` Mike Looijmans
2013-02-10 14:55 ` Martin Jansa
2013-02-10 19:02 ` Mike Looijmans
2013-02-10 19:59 ` Martin Jansa
2013-02-18 11:04 ` Mike Looijmans [this message]
2013-02-18 11:11 ` OE-core] How do I find out why are packages being rebuilt? Burton, Ross
2013-02-18 13:14 ` Mike Looijmans
2013-02-18 13:19 ` Burton, Ross
2013-02-18 17:28 ` Martin Jansa
2013-01-29 11:27 ` Multiple MACHINE building is broken in OE-core? Martin Jansa
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=51220AAC.8080201@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.