When building a new kernel, or testing and update to the kernel there are a set of packages that are sensitive to APIs, build system and other changes associated with the kernel.
After building this recipe, we can be reasonably sure that a new kernel package and coupled userspace have been built, installed and tested via a single image. Signed-off-by: Bruce Ashfield <[email protected]> --- meta/recipes-extended/images/core-image-kernel-dev.bb | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 meta/recipes-extended/images/core-image-kernel-dev.bb diff --git a/meta/recipes-extended/images/core-image-kernel-dev.bb b/meta/recipes-extended/images/core-image-kernel-dev.bb new file mode 100644 index 000000000000..d14f658726ab --- /dev/null +++ b/meta/recipes-extended/images/core-image-kernel-dev.bb @@ -0,0 +1,17 @@ +DESCRIPTION = "A development image that builds the kernel and packages that are \ +sensitive to kernel updates and version changes" + +# Could also be core-image-basic, but we'll keep this small for now +require recipes-core/images/core-image-minimal.bb + +KERNEL_DEV_UTILS ?= "dropbear" +KERNEL_DEV_TOOLS ?= "packagegroup-core-tools-profile packagegroup-core-buildessential kernel-devsrc" +KERNEL_DEV_MODULE ?= "" + +CORE_IMAGE_EXTRA_INSTALL += "${KERNEL_DEV_MODULE} \ + ${KERNEL_DEV_UTILS} \ + ${KERNEL_DEV_TOOLS} \ + " + +# We need extra space for things like kernel builds, etc. +IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000" -- 2.1.0 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
