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. (From OE-Core rev: 568b81b5102213643e382d31a4e5e56f90ee6ff9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
eb7b1a58ce
commit
7fb583aa95
|
@ -93,10 +93,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
|
||||
|
||||
|
|
Loading…
Reference in New Issue