When installing the ext sdk, buildtools is extracted and installed as
well. The tar file containing buildtools isn't used after installation
so was wasted space and clutter.
[YOCTO #9172]
Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com>
---
meta/classes/populate_sdk_ext.bbclass | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/classes/populate_sdk_ext.bbclass
b/meta/classes/populate_sdk_ext.bbclass
index 9e2fc61..f927cb9 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -313,6 +313,9 @@ sdk_ext_postinst() {
cd $target_sdk_dir
printf "buildtools\ny" | ./*buildtools-nativesdk-standalone* >
/dev/null || ( printf 'ERROR: buildtools installation failed\n' ; exit 1 )
+ # Delete the buildtools tar file since it won't be used again
+ rm ./*buildtools-nativesdk-standalone*.sh -f
+
# Make sure when the user sets up the environment, they also get
# the buildtools-tarball tools in their path.
env_setup_script="$target_sdk_dir/environment-setup-${REAL_MULTIMACH_TARGET_SYS}"
--
2.5.0
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
