bitbake rootfs大，核心映像最小

Question

First, I generated a core-image-sato target image using bitbake. Then after that I generated core-image-minimal target. The root file system generated still contains the contents/packages of the existing target.

How can I avoid this and have a minimal root file system

Answer 1

I think core-image-sato is build with X11 and core-image-minimal is without X11 . both are fully deferent images.

so in your deploy/images/your-board/ . should have core-image-sato-*-rootfs-* will present also core-image-minimal-*-rootfs* present.

Those things you can not delete if you delete core-image-sato- -rootfs- next time you can not able to compile core-image-sato. it will give errors.

Answer 2

Did this in latest Poky 2.6 - Try to use poky > 2.1

bitbake core-image-minimal & bitbake core-image-sato generates different set of images.

• check if you have enough disk space!
• check that you are not adding extra packages in your /build/conf/local.config
• check that you are using different local.config files while bitbaking core-image-minimal and core-image-sato. (If you have added packages while bitbaking sato then those packages will be added while bitbaking minimal, if you are using same local.config)

Just a suggestion, not that you have to do it:
If you are bitbaking for the first time use default /build/conf/local.config and /build/conf/bblayers.conf (uncommenting DL_DIR, SSTATE_DIR, TMPDIR will be beneficial though)