On 11/04/2011 10:18 PM, Koen Kooi wrote:
Op 4 nov. 2011, om 18:52 heeft Paul Eggleton het volgende geschreven:
If the user has set their own value for IMAGE_FSTYPES, they may have
disabled the cpio.gz image type, preventing the initramfs from being
produced in the format that image-live.bbclass expects; so force
IMAGE_FSTYPES to cpio.gz within the initramfs image recipe.
Signed-off-by: Paul Eggleton<paul.eggle...@linux.intel.com>
---
.../images/core-image-minimal-initramfs.bb | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/meta/recipes-core/images/core-image-minimal-initramfs.bb
b/meta/recipes-core/images/core-image-minimal-initramfs.bb
index 0bac27a..e4d0e51 100644
--- a/meta/recipes-core/images/core-image-minimal-initramfs.bb
+++ b/meta/recipes-core/images/core-image-minimal-initramfs.bb
@@ -13,3 +13,4 @@ LICENSE = "MIT"
inherit core-image
IMAGE_ROOTFS_SIZE = "8192"
+IMAGE_FSTYPES = "cpio.gz"
_append or += would give less suprises.
This was merged as IMAGE_FSTYPES =+ "cpio.gz"
Now this brings problems if I have IMAGE_FSTYPES += "live" in my
local.conf / BSP machine.conf.
1) OE tries to generate hddimg for this initramfs image, which is
strange idea
2) If OE is trying to generate bootimg (hddimg) when the kernel is not
yet deployed, building fails (as bootimg can't find a deployed kernel to
put into hddimg).
Please revert this back to original patch as proposed by Paul.
--
With best wishes
Dmitry
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
