**** BEGIN LOGGING AT Mon May 22 03:00:02 2017 May 22 06:50:42 good morning May 22 08:12:14 hi. looking at image_types.bbclass, I can see that EXTRA_IMAGECMD is defined for several types of image, e.g. with _ext2, _ext4, ... however I fail to see how the variable is parsed/used. imho it is not even parsed anywhere. am i missing anything? May 22 08:13:08 IMAGE_DEPENDS is constructed in a same way, but that variable is read properly, e.g. adddep(d.getVar('IMAGE_DEPENDS_%s' % basetype) , deps) May 22 10:10:31 ndec: it's part of the image command for specific types, yes... I think that's the only way it's referred to May 22 10:11:16 hi bluelightning. i don't get it. where is it used? May 22 10:11:33 ndec: IMAGE_CMD_ext2 = "oe_mkext234fs ext2 ${EXTRA_IMAGECMD}" May 22 10:11:51 for example May 22 10:11:59 yes. that i see. but it's $EXTRA_IMAGECMD, not $EXTRA_IMAGECMD_ext2 May 22 10:12:20 EXTRA_IMAGECMD is always emtpy. May 22 10:12:24 ndec: ah right, so that's just the general override mechanism used in the image types code, one sec May 22 10:12:51 well, that's what i thought.. but i couldn't see it used for EXTRA_IMAGECMD. May 22 10:14:03 search for OVERRIDES in image.bbclass and you'll find how that all gets set May 22 10:19:04 bluelightning: ah. interesting. i missed that. thought i had tried bitbake -e | grep ^OVERRIDES and it didn't show up. May 22 10:20:13 right, yeah, this wouldn't show up thre May 22 10:20:18 *there May 22 10:20:47 bluelightning: well, thanks.. so my patch 3/3 from today needs an update then! thanks! May 22 10:21:41 no worries May 22 10:24:24 i am not worried.. i expect bigger non technical issues with this patch set ;-) **** ENDING LOGGING AT Tue May 23 03:00:01 2017