Skip to contentSkip to conversation

multilib: Drop populate_sdk variable manipulation

PATCH New Richard Purdie 1 participant 1 message Sep 26, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 multilib: Drop populate_sdk variable manipulation

I believe this code dates from previous times when we didn't extend the TOOLCHAIN_TARGET* variables to cover all multilibs. We now do this so this code acutally breaks things by removing the non-multilib variants.

By changing this, a multilib SDK now contains both sets of base libraries which matches the tools we ship with it. If the user wishes to customise, this also becomes easier.

meta/classes/multilib.bbclass +0 -4
index cbf1fb8..052f911 100644
@@ -94,10 +94,6 @@ python __anonymous () {
         # FIXME, we need to map this to something, not delete it!
         d.setVar("PACKAGE_INSTALL_ATTEMPTONLY", "")
 
-    if bb.data.inherits_class('populate_sdk_base', d):
-        clsextend.map_depends_variable("TOOLCHAIN_TARGET_TASK")
-        clsextend.map_depends_variable("TOOLCHAIN_TARGET_TASK_ATTEMPTONLY")
-
     if bb.data.inherits_class('image', d):
         return