On Wed, 6 Sept 2023 at 21:28, Alexander Kanavin via
lists.openembedded.org <[email protected]>
wrote:
> > This doesn't just force ordering but means target will always now
> > trigger the native sysroot as a dependency. We don't want to do that...
>
> But I think we do. Target is using executables from native sysroot
> such as user management utilities from shadow-native, and they won't
> be otherwise present there.
By the way extend_recipe_sysroot() is already doing:
staging_populate_sysroot_dir(recipesysroot,
recipesysrootnative, True, d)
staging_populate_sysroot_dir(recipesysroot,
recipesysrootnative, False, d)
so just calling one after the other in a single task. Why
build-sysroots recipe has those as separate tasks I'm not sure, but
they should either be folded into one task, or be strictly ordered and
required. Unless I am missing something.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187352):
https://lists.openembedded.org/g/openembedded-core/message/187352
Mute This Topic: https://lists.openembedded.org/mt/101197363/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
