From: Patrick Ohly <patrick.ohly@intel.com>
To: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: runqemu + multiconfig
Date: Thu, 12 Jan 2017 15:32:30 +0100 [thread overview]
Message-ID: <1484231550.2137.141.camel@intel.com> (raw)
Hello!
runqemu works okay in a multiconfig setup, but one has to be careful
about how one sets MACHINE in the base configuration (aka local.conf):
it has to be done with ?= and not =
Example:
local.conf:
MACHINE ?= "intel-corei7-64"
BBMULTICONFIG = "core2 quark"
conf/multiconfig/quark.conf:
MACHINE = "intel-quark"
conf/multiconfig/core2.conf:
MACHINE = "intel-core2-32"
$ runqemu refkit-image-noswupd dsk intel-core2-32 ovmf
runqemu - INFO - Assuming MACHINE = intel-core2-32
runqemu - INFO - Running MACHINE=intel-core2-32 bitbake -e...
runqemu - INFO - MACHINE: intel-core2-32
runqemu - INFO - DEPLOY_DIR_IMAGE: .../tmp-glibc/deploy/images/intel-core2-32
runqemu - INFO - CONFFILE: .../tmp-glibc/deploy/images/intel-core2-32/...-intel-core2-32.qemuboot.conf
When using MACHINE = "intel-corei7-64" in local.conf, overriding the
MACHINE with "MACHINE=intel-core2-32 bitbake -e..." fails and runqemu
ends up using the image directory of the base configuration:
$ runqemu refkit-image-noswupd dsk intel-core2-32 ovmf
runqemu - INFO - Assuming MACHINE = intel-core2-32
runqemu - INFO - Running MACHINE=intel-core2-32 bitbake -e...
runqemu - INFO - MACHINE: intel-core2-32
runqemu - INFO - DEPLOY_DIR_IMAGE: .../tmp-glibc/deploy/images/intel-corei7-64
Traceback (most recent call last):
....
Exception: Failed to find <image>.qemuboot.conf!
This was with the patch for qemu support in meta-intel and the OVMF
firmware, but should also apply to the normal qemux86/qemux86-64.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
reply other threads:[~2017-01-12 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1484231550.2137.141.camel@intel.com \
--to=patrick.ohly@intel.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