We're building several images which share a standard parition layout defined in a .wks file and built through the IMAGE_CMD_wic function defined in image_types.bbclass. Because that function looks for ${IMAGE_BASENAME}.${MACHINE}.wks and ${IMAGE_BASENAME}.wks we have to symlink our base .wks to the appropriate IMAGE_BASENAME's for the other images. This is even messier for multiple layers that build on a shared base layer and each define images. It would be really nice if we could define a variable, i.e. in our shared image class, that tells the image generation code where to load a shared .wks file from.
Sent implementation for review: http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115798.html
Sent v2: http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115808.html
the implementation of wks 'include' statement was accepted to master: http://cgit.openembedded.org/openembedded-core/commit/?id=3695962ba4b685f304f1039978cec60d1b1712e3
Verified on master: 152914f2983c5d69001de1d46ce99547fa1e75fe The directdisk.wks , directdisk-bootloader-config.wks and qemux86-directdisk.wks are including the common.wks.inc. Building directdisk, directdisk-bootloader-config and qemux86-directdisk works as before.