From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Multiple MACHINE building is broken in OE-core?
Date: Tue, 29 Jan 2013 10:29:07 +0100 [thread overview]
Message-ID: <51079663.60504@topic.nl> (raw)
I often have several hardware boards sharing 99% of periferals and
configuration. Usually they all have the exact same CPU, and the
difference is in the minor details like the screen resolution.
In "classic" OE I was used to sharing the work, by just changing the
MACHINE variable I could create an image for a slightly changed board in
a matter of minutes.
In OE-core this seems to be horribly broken, unless there's some other
procedure to follow.
If I change the MACHINE, it insists on rebuilding all kinds of packages
that don't need rebuilding at all. Instead of minutes, it takes an hour
to switch machines. And if I change back, the same thing happens all
over again.
In addition to needlessly rebuilding dozens of packages for the same
architecture, it often "starts" halfway through, so it tries to run the
"deploy" phase for a package while the workspace has already been
removed in the rm_work phase of the previous build. Which fails, so I
have to manually reset stamps for that package and let it start over
again (while usually the package shouldn't be rebuilt in the first place).
Is building for several machines no longer supported in OE-core? Or is
there some secret way of setting up directories and variables that will
make it work as it used to?
--
Mike Looijmans - TOPIC Automation
next reply other threads:[~2013-01-29 9:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:29 Mike Looijmans [this message]
2013-01-29 9:40 ` Multiple MACHINE building is broken in OE-core? 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 ` OE-core] How do I find out why are packages being rebuilt? Mike Looijmans
2013-02-18 11:11 ` 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
2013-02-06 8:02 Cooper Jr., Franklin
2013-02-06 8:56 ` Martin Jansa
2013-02-07 18:00 ` Cooper Jr., Franklin
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=51079663.60504@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.