Bug 6279

Summary:	default bitbake qemu build might create too much in do_rootfs
Product:	[Build System, Metadata & Runtime] Meta-yocto	Reporter:	Volker <lists.volker>
Component:	meta-yocto	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED INVALID	QA Contact:
Severity:	enhancement
Priority:	Undecided	CC:	dvhart, poky.bs.watcher, poky.watcher
Version:	1.5.1
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Volker 2014-05-07 17:09:30 UTC

bitbake <distro> creates by default settings qemu images that can then be used by runqemu. That allows rapid tests on changes at the work station.

bitbake is smart and does not re-build everything but only changed parts which is good and increase the development and testing speed.

Yet it seems to me (without the full understanding on how runqemu image creation works) that the default qemu build creates more files as needed in the do_rootfs step as needed by runqemu. It might be more efficient to only create the files that are needed.


Just feedback. :)

Comment 1 Darren Hart 2014-05-08 14:54:37 UTC

Hi Volker,

Thanks for the feedback and taking the time to file a bug. Unfortunately, bugs need to be specific in nature in order for us to act on them. I'll be rejecting this one as invalid as there isn't anything specific we can address here.

However, if you can consider the following you can open a new bug with more information:

1) Which image target (what you referred to as <fistro> here) are you referring to? core-image-sato-sdk? core-image-minimal?

2) Which packages in particular (or files) would you like to see removed?

3) Which DISTRO= are you building? This is specified in local.conf, the default is  "poky", but "poky-tiny" also exists, which shrinks the core-image-minimal image quite a bit.