8848 2015-12-22 09:57:47 +0000 Would like to be able to share a single Kickstart partition layout definition (.wks) between several images 2016-02-17 16:01:25 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.0 x86 Multiple VERIFIED FIXED Medium+ enhancement 2.1 M3 1 joshuagloe eduard.bartosh alexandru.c.georgescu ross.burton daniel.alexandrux.istrate --- --- Yes (doc changes required) oldest_to_newest 57423 0 joshuagloe 2015-12-22 09:57:47 +0000 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. 57959 1 eduard.bartosh 2016-01-19 17:37:38 +0000 Sent implementation for review: http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115798.html 57966 2 eduard.bartosh 2016-01-19 18:55:45 +0000 Sent v2: http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115808.html 58129 3 eduard.bartosh 2016-01-22 10:24:15 +0000 the implementation of wks 'include' statement was accepted to master: http://cgit.openembedded.org/openembedded-core/commit/?id=3695962ba4b685f304f1039978cec60d1b1712e3 59156 4 daniel.alexandrux.istrate 2016-02-17 16:01:25 +0000 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.