From: Thomas Kristensen <[email protected]>

If you wish to change the install/unpack method of the sdk, this can now be 
done by making
your own create_shar method, and setting a POPULATE_SDK_CREATE_SHAR_COMMAND 
variable to your
new create_shar function.

Signed-off-by: Thomas Kristensen <[email protected]>
Signed-off-by: Martin Ertsaas <[email protected]>
---
 meta/classes/populate_sdk_base.bbclass |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/meta/classes/populate_sdk_base.bbclass 
b/meta/classes/populate_sdk_base.bbclass
index 1c151d7..53b11a3 100644
--- a/meta/classes/populate_sdk_base.bbclass
+++ b/meta/classes/populate_sdk_base.bbclass
@@ -24,6 +24,8 @@ PID = "${@os.getpid()}"
 
 EXCLUDE_FROM_WORLD = "1"
 
+POPULATE_SDK_CREATE_SHAR_COMMAND ?= "create_shar"
+
 python () {
     # If we don't do this we try and run the mapping hooks while parsing which 
is slow
     # bitbake should really provide something to let us know this...
@@ -56,7 +58,7 @@ fakeroot python do_populate_sdk() {
 
     bb.build.exec_func("tar_sdk", d)
 
-    bb.build.exec_func("create_shar", d)
+    bb.build.exec_func(d.getVar("POPULATE_SDK_CREATE_SHAR_COMMAND", True), d)
 }
 
 fakeroot populate_sdk_image() {
-- 
1.7.8.6


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to