classes/populate_sdk_ext: avoid poky-specific buildtools naming

Only poky sets SDK_NAME to include ${IMAGE_BASENAME} (i.e. ${PN}), so we
can't assume the buildtools filename will include it here. Change it to
look for a file with "buildtools-nativesdk-standalone" in the name
(the buildtools-tarball recipe itself sets TOOLCHAIN_OUTPUTNAME to
include this.)

(From OE-Core rev: 78ea4fcdea468888c0faef22a95dea7015a91df2)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass
index a36bf16c78..8509f0c25b 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -189,7 +189,7 @@ SDK_PRE_INSTALL_COMMAND_task-populate-sdk-ext = "${sdk_ext_preinst}"
 sdk_ext_postinst() {
         printf "\nExtracting buildtools...\n"
         cd $target_sdk_dir
-        printf "buildtools\ny" | ./*buildtools-tarball* > /dev/null
+        printf "buildtools\ny" | ./*buildtools-nativesdk-standalone* > /dev/null
 
         # Make sure when the user sets up the environment, they also get
         # the buildtools-tarball tools in their path.