summaryrefslogtreecommitdiffstats
path: root/meta
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2011-06-29 12:16:07 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-06-30 20:56:34 +0100
commit64497638e70c97f417c2bcdaf99ffcc843ad58ec (patch)
tree736ef729cce30b2298436e846b52cabda48b1962 /meta
parent53dfb5f55d51cf10e2efc029421255a1d0fdd3ce (diff)
downloadpoky-64497638e70c97f417c2bcdaf99ffcc843ad58ec.tar.gz
kernel: move menuconfig task after configure
Fixes [YOCTO 1136] linux-yocto adds some configure steps that are necessary to prepare the source tree after the do_patch task. This causes a "-c menuconfig" to fail in a clean build tree. Typical use of menuconfig should be to modify the config provided by the recipe being built. It therefor makes sense for the menuconfig task to come after the configure task. This also happens to fix the issue seen with the linux-yocto kernel recipe. (From OE-Core rev: 829dd1d7ca99ec6228d2705cdece4727232797d3) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta')
-rw-r--r--meta/classes/kernel.bbclass2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index fd27832510..f282a57f6d 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -194,7 +194,7 @@ do_menuconfig() {
194 fi 194 fi
195} 195}
196do_menuconfig[nostamp] = "1" 196do_menuconfig[nostamp] = "1"
197addtask menuconfig after do_patch 197addtask menuconfig after do_configure
198 198
199pkg_postinst_kernel () { 199pkg_postinst_kernel () {
200 cd /${KERNEL_IMAGEDEST}; update-alternatives --install /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE} ${KERNEL_IMAGETYPE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION} ${KERNEL_PRIORITY} || true 200 cd /${KERNEL_IMAGEDEST}; update-alternatives --install /${KERNEL_IMAGEDEST}/${KERNEL_IMAGETYPE} ${KERNEL_IMAGETYPE} ${KERNEL_IMAGETYPE}-${KERNEL_VERSION} ${KERNEL_PRIORITY} || true