]> code.ossystems Code Review - openembedded-core.git/commit
bitbake.conf: include machine name in DEPLOY_DIR_IMAGE
authorPaul Eggleton <paul.eggleton@linux.intel.com>
Thu, 12 Sep 2013 11:04:52 +0000 (12:04 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 12 Sep 2013 15:48:38 +0000 (16:48 +0100)
commit7e90261aec61f79680b5eaeaf5b18c7b795412a4
treee971aa90f82a754e6d005533036702903a450b72
parentebfdddc23ff78231a819c62c8ffcced9633aa08b
bitbake.conf: include machine name in DEPLOY_DIR_IMAGE

This allows a clean seperation between image outputs from different
machines, and makes it possible to have convenience symlinks to make
the output ready to deploy.

This did require some surgery in runqemu; if explicit paths to the image
and kernel are not supplied then DEPLOY_DIR_IMAGE needs to be determined
from bitbake or set in the environment. However the script does try to
avoid requiring it unless it really is needed. Corresponding changes
were made in the automated testing code as well.

Based on an RFC patch by Koen Kooi <koen@dominion.thruhere.net>

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/testimage.bbclass
meta/conf/bitbake.conf
meta/lib/oeqa/utils/qemurunner.py
scripts/runqemu