When running "wic help overview", among various other examples, the help shows how to specify manually on the command line various parameters and a non-canned wks file, but it doesn't show the content of the custom .wks file used. The text starts with "Here's an example that doesn't take the easy way out ..." It would seem appropriate to provide also the content of the ~/test.wks file referred by the example, as it is not a canned one.
I'm going to change help to this: Here's an example that doesn't take the easy way out and manually specifies each build artifact, along with a non-canned .wks file, and also uses the -o option to have wic create the output somewhere other than the default /var/tmp/wic: $ wic create ./test.wks -o ./out -r tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs -b tmp/sysroots/qemux86-64/usr/share -k tmp/deploy/images/qemux86-64 -n tmp/sysroots/x86_64-linux -o Creating image(s)... Info: The new image(s) can be found here: out/build/test-201507211313-sda.direct The following build artifacts were used to create the image(s): ROOTFS_DIR: tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs BOOTIMG_DIR: tmp/sysroots/qemux86-64/usr/share KERNEL_DIR: tmp/deploy/images/qemux86-64 NATIVE_SYSROOT: tmp/sysroots/x86_64-linux The image(s) were created using OE kickstart file: ./test.wks Here is a content of test.wks: part /boot --source bootimg-pcbios --ondisk sda --label boot --active --align 1024 part / --source rootfs --ondisk sda --fstype=ext3 --label platform --align 1024 bootloader --timeout=0 --append="rootwait rootfstype=ext3 video=vesafb vga=0x318 console=tty0" Igor, please confirm it's ok for you.
Submitted fix for review: http://lists.openembedded.org/pipermail/openembedded-core/2015-August/108258.html
Fix has been merged to master: http://cgit.openembedded.org/openembedded-core/commit/?id=68d391eaf4fe9fc37e3278255d5da170f98b8763
Verified on master: c1df471feacaf2590216aa476ce242908dac38cf