Re: [wic][PATCH] wic: Implement --build-rootfs command line option

["João Henrique Ferreira de Freitas" <joaohf@gmail.com>]

Hi

On 09/04/2015 16:12, Ed Bartosh wrote:
> On Wed, Apr 08, 2015 at 07:18:40PM -0300, João Henrique Ferreira de Freitas wrote:
>> Hi Ed,
>>
>> I liked.
>>
>> Two points:
>>
>> - How about if user sets INHERIT = "rm_work"? I mean the image
>> recipe will be rm, right? I always put my images in RM_WORK_EXCLUDE
>> so wic can use it.
>>
> rm_work removes artifacts required by wic. Wic will complain that rootfs
> can't be found. There is a bug about i https://bugzilla.yoctoproject.org/show_bug.cgi?id=7042
> I closed it as not a bug as wic uses build artifacts by design.

I agree.

>> - What will be the behavior if: wic create test-image-4Gb -e
>> test-image --rootfs rootfs1=test-image --rootfs
>> rootfs2=bringup-image -f. A believed that only 'test-image' will be
>> build. Right?
>>
> I don't fully understand command line options in your example, but generally you're right.
> wic will take image name from -e option and run "bitbake test-image" in this case.

This thread explain the above command line options: 
http://lists.openembedded.org/pipermail/openembedded-core/2014-March/091185.html

Usually I run this sequence:

bitbake test-image
bitbate bringup-image

wic create test-image-4Gb -e test-image --rootfs rootfs1=test-image --rootfs rootfs2=bringup-image

So wic will create a directdisk with two images where each one will be 
place on specific partition.

I  guess if '-f' is used, wic could call bitbake to 'test-image' and 
'bringup-image'.

Thanks.