---- On Tue, 24 May 2016 15:51:45 -0400 Ed Bartosh <ed.bart...@linux.intel.com> wrote ---- > On Mon, May 23, 2016 at 08:13:28AM -0400, Ian Geiser wrote: > > > On Thu, May 19, 2016 at 05:52:45AM -0400, Ian Geiser wrote:
[...snip...] > How about creating recipe to prepare content or your boot partition and then > using --source rootfs --rootfs-dir=<your recipe> ? > This is much more generic way of creating partitioned images from my > point of view. Image recipes should take care of content and wic takes care > of > putting that content into partitions according to the partitioning > scheme described in .wks > > Does it make sense for you? I am at a loss how to do this because it is a efi system partition. Really all it needs is the kernel, initramfs and bootx64. I see how to do the kernel and the bootx64 in the existing plugin. What I get turned around with is the initramfs. It seems like there is no way to put that in, or use a kernel with the initramfs appended. Is this a limitation that is fixed by "send a patch" or am I missing something there. > > > > > > You can probably do the same by using wic plugins, but I'd not suggest > > > to go this way. Using wic image type is simpler, more consistent, > > easier to do and provides higher level of automation. > > > > Is using the wic image type and a plugin mutually exclusive? > No, not at all. However, I personally found the way I described above > more consistent, flexible and easy to implement and maintain. I am not groking this concept because it seems without a robust library of plugins the wks files become very hard to implement. Is this true, or am I again missing something obvious. Thanks for your patience. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core