On Tue, 2017-03-14 at 20:06 +0200, Ed Bartosh wrote: > On Tue, Mar 14, 2017 at 06:49:45PM +0100, Patrick Ohly wrote: > > > > > It's not a big deal to run wic sequentially to produce multiple images, > > > but it will create more problems than it solves I believe. It will be > > > slower and > > > will make a mess in image naming in deploy directory. > > > > I personally would prefer to support generating more than one wic image > > per image recipe. The different output files could be distinguished with > > an additional suffix (".efi.wic", ".live.wiC", etc.) where the suffix is > > either specified by the WKS file or the configuration where the WKS file > > is selected - the latter might be a bit more flexible. > > > > From my point of view ths would be against the current design of oe > image building susbsystem. It would be also more complex and slower > unless we'll find a way to dynamically generate multiple image creation > tasks per one recipe and run them in parallel. In this case it will be > even more complex.
That's a good point. However, directly sharing the content of the build directory from different recipes is also against the OE design and requires special attention, for example to suppressing the do_rootfs task in one recipe and preventing do_rm_work in the other. Either way, something that works out of the box might be useful. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core