On 05/15/2012 06:25 PM, Christopher Larson wrote: > From: Christopher Larson <[email protected]> > > It's common to provide a non-machine-suffixed link in DEPLOY_DIR_IMAGE, so > let's be consistent and do so here as well.
This of course means that building two machines in the same build dir will result in overwriting the latest non-machine-suffixed link (provided they are the same image type). I agree that sometimes I wished I just had a bzImage, but the current behavior seems more robust, consistent, and is less prone to user error. Is there a reason other than aligning with what other packages do to do this? Which packages do this? -- Darren > > Signed-off-by: Christopher Larson <[email protected]> > --- > meta/classes/kernel.bbclass | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass > index a85f130..90af597 100644 > --- a/meta/classes/kernel.bbclass > +++ b/meta/classes/kernel.bbclass > @@ -538,6 +538,7 @@ kernel_do_deploy() { > cd ${DEPLOYDIR} > rm -f ${KERNEL_IMAGE_SYMLINK_NAME}.bin > ln -sf ${KERNEL_IMAGE_BASE_NAME}.bin ${KERNEL_IMAGE_SYMLINK_NAME}.bin > + ln -sf ${KERNEL_IMAGE_BASE_NAME}.bin ${KERNEL_IMAGETYPE} > > cp ${COREBASE}/meta/files/deploydir_readme.txt > ${DEPLOYDIR}/README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt > } -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
