| Message ID | 20261119055929.3286725-1-joerg.vehlow@emlix.com |
|---|---|
| State | Under Review |
| Headers | show |
| Series | staging: allow special handling of initial-recipes also for native | expand |
diff --git a/meta/classes-global/staging.bbclass b/meta/classes-global/staging.bbclass index 20340a16e1..6438f6bddd 100644 --- a/meta/classes-global/staging.bbclass +++ b/meta/classes-global/staging.bbclass @@ -453,7 +453,7 @@ python extend_recipe_sysroot() { installed = [] for dep in configuredeps: c = setscenedeps[dep][0] - if mytaskname in ["do_sdk_depends", "do_populate_sdk_ext"] and c.endswith("-initial"): + if mytaskname in ["do_sdk_depends", "do_populate_sdk_ext"] and (c.endswith("-initial") or c.endswith("-initial-native")): bb.note("Skipping initial setscene dependency %s for installation into the sysroot" % c) continue installed.append(c)
Sometimes a native recipe also needs bootstrapping (e.g. for ada, rust or go) -inital-native recipes are already handled different in bitbake.conf (both suffixes are stripped). During staging for the esdk these packages should also not be staged in the sysroot as they might conflict like libgcc-initial does. Signed-off-by: Joerg Vehlow <joerg.vehlow@emlix.com> --- meta/classes-global/staging.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)