[yocto] live" image: iso and ext4 artifacts
Takashi Matsuzawa
tmatsuzawa at xevo.com
Fri Dec 16 13:58:35 PST 2016
Hello.
Thanks it worked for .iso files.
I have found that this really is a save for build time also.
________________________________
From: Jussi Kukkonen <jussi.kukkonen at intel.com>
Sent: Friday, December 16, 2016 6:22 PM
To: Takashi Matsuzawa
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] live" image: iso and ext4 artifacts
On 15 December 2016 at 09:30, Takashi Matsuzawa <tmatsuzawa at uievolution.com<mailto:tmatsuzawa at uievolution.com>> wrote:
>
> Hello Yocto.
>
> I am trying x86-64 BSP image (based on jethro version).
> It has following root filesystem type, and it generats xxxx.hddimg file that I am using.
>
> > IMAGE_FSTYPES = "live"
>
> The issue is that in addition to xxxx.hddimg, it produces following image files and it sometimes cause lack of disk space error on my build PC.
>
> > 2422489088 xxxx-intel-corei7-64-20161215004421.hddimg
> > 2402287616 xxxx-intel-corei7-64-20161215004421.iso
> > 2368578560 xxxx-intel-corei7-64-20161215004421.rootfs.ext4
>
> I do not need xxx.iso and xxxx.ext4 files as final output, though I understand that xxxx.ext4 file may have been used to produce xxx.hddimg file.
I think you should be able to define NOISO=1.
The rootfs is indeed used to produce the actual images, you could delete it afterwards... but before you spend valuable time writing shell scripts, consider a new SSD: 500GB is probably less than 150EUR by now.
Jussi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161216/809c1602/attachment.html>
More information about the yocto
mailing list