]> code.ossystems Code Review - openembedded-core.git/commit
image_types.bbclass: Embed IMAGE_NAME in ubinize config file
authorDrew Moseley <drew_moseley@mentor.com>
Fri, 5 Feb 2016 17:56:20 +0000 (10:56 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 7 Feb 2016 17:29:45 +0000 (17:29 +0000)
commitbc7643846f9fcef13a02f9299faa5454c843e8b1
tree0596bf641bd11c68616cbb050c403da1ee03953b
parent668f56bb2496aa0e7b5b71fb54b45371bbf6653c
image_types.bbclass: Embed IMAGE_NAME in ubinize config file

When using the FSTYPE multiubi, make sure that each image build
has a unique config file.  Without this there is a race condition
when building multiple images in a single bitbake command which
results in errors similar to:

    ERROR: Error: The image creation script
    'blah/tmp/work/blah/core-image-base/1.0-r0/temp/create_image.multiubi' returned 1:
    iniparser: cannot open ubinize_normal.cfg
    ubinize: error!: cannot load the input ini file "ubinize_normal.cfg"
    mv: cannot stat 'ubinize_normal.cfg': No such file or directory
    WARNING: blah/tmp/work/blah/core-image-base/1.0-r0/temp/create_image.multiubi:1 exit 1 from
      mv ubinize${vname}.cfg blahtmp/deploy/images/blah/

Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/classes/image_types.bbclass