**** BEGIN LOGGING AT Mon Dec 26 02:59:56 2022
Dec 26 18:30:37 <zhmylove> Hey all! I have recipe A-native which creates an empty file in "/" on do_install() and recipe B which depends on A-native. Are there any ideas, why there are no traces of the files installed by A in ${WORKDIR} of B?
Dec 26 18:39:29 <JaMa> zhmylove: only some files are staged in sysroot by default (like libs, headers), see sysroot_stage_all which you can extend to stage files you need from A
Dec 26 18:42:30 <JaMa> since 2016 with oe-core commit 80e7e7f78d957b8159bede2a5cd5614d8d73039c you can often just extend SYSROOT_DIRS list
Dec 26 18:51:08 <zhmylove> JaMa: thank you! BTW should I extend them in recipe A?
Dec 26 18:56:30 <zhmylove> I'm asking as it's still not working well: https://pastebin.com/n1Xz4Hev
Dec 26 19:01:47 <JaMa> from this output I don't see what would be wrong, easier to look in the WORKDIR with shell
Dec 26 21:29:56 <dv_> would you add "TOOLCHAIN_HOST_TASK:append" to a distro config?
Dec 26 21:30:22 <dv_> example: `TOOLCHAIN_HOST_TASK:append = " nativesdk-meson nativesdk-qttools-tools "`
Dec 26 21:30:27 <dv_> or is this not a good idea?
Dec 26 22:19:48 <JaMa> dv_: I wouldn't, not every recipe might need meson or qttools, why not .bbappend?
Dec 26 22:23:38 <dv_> ah, forgot to add, this is for a system that uses qt pretty much everywhere
Dec 26 22:25:30 <dv_> so considering that, can this still break things?
Dec 26 22:39:22 <JaMa> I would still add it in some recipe or bbappend, which could be specific for that DISTRO, but you would be able to build some really small sdk for e.g. external initramfs developers which might not need meson and qttools
Dec 26 22:40:46 <JaMa> YMMV e.g. if you have a lot of different SDKs which don't share some common bbclass or .inc file and all of them really need meson and qttools and you really don't want to support anything else on that DISTRO
**** ENDING LOGGING AT Tue Dec 27 02:59:56 2022