On 2016-01-25 10:07 AM, Richard Purdie wrote:
If we don't do this, the deploy sstate object contains an every
increasing number of modules tarballs and kernel images, one per
execution of "-c deploy -f".
Stupid question, since my sstate/deploy foo is weak at times.
Does this mean that only a single set of modules + kernel images
will be in tmp/deploy ? Or is it only sstate that is being
cleaned ?
I sometimes need multiple copies around for debug purposes, so
I'm wondering if that is still possible with this change ?
Bruce
Cleaning the directory before we start makes things much tidier.
Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index dee6f7d..f37affc 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -511,6 +511,7 @@ kernel_do_deploy() {
ln -sf ${initramfs_base_name}.bin ${initramfs_symlink_name}.bin
fi
}
+do_deploy[cleandirs] = "${DEPLOYDIR}"
do_deploy[dirs] = "${DEPLOYDIR} ${B}"
do_deploy[prefuncs] += "package_get_auto_pr"
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
