From 4775af4650f389e0a294e88acde04827946c0931 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 28 Nov 2016 15:22:45 -0800 Subject: ref-manual: Added KERNEL_IMAGE_BASE_NAME change to 2.2 migration The fact that the OpenEmbedded build system can now build multiple image types caused the KERNEL_IMAGE_BASE_NAME variable to have the KERNEL_IMAGETYPE portion removed. This could cause existing recipes that use the KERNEL_IMAGE_BASE_NAME variable directly issues. I added a section indicating that the user should address those recipes to avoid problems. (From yocto-docs rev: c433fca3840440c14bb364a51afc5c3c2bfc7c88) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/migration.xml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'documentation/ref-manual/migration.xml') diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index f9e418c769..2bdb542ec1 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -3620,6 +3620,27 @@ $ runqemu qemux86-64 tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64. +
+ <filename>KERNEL_IMAGE_BASE_NAME</filename> no Longer Uses <filename>KERNEL_IMAGETYPE</filename> + + + The + KERNEL_IMAGE_BASE_NAME + variable no longer uses the + KERNEL_IMAGETYPE + variable to create the image's base name. + Because the OpenEmbedded build system can now build multiple kernel + image types, this part of the kernel image base name as been + removed leaving only the following: + + KERNEL_IMAGE_BASE_NAME ?= "${PKGE}-${PKGV}-${PKGR}-${MACHINE}-${DATETIME} + + If you have recipes or classes that use + KERNEL_IMAGE_BASE_NAME directly, you might + need to update the references to ensure they continue to work. + +
+
BitBake Changes -- cgit v1.2.3-54-g00ecf