are you both using systemd or sysvinit

if its eSDK then you can, with standard application SDK not so much.

#sdk #zeus #toolchain

look into package-split/ directory inside googletest build area and see how things changes when you use SOLIBS option. I wonder why its ignoring .h files

yes was seeing same. Can you turn this into a patch and send?

its trying to create the file with 0600 mask. I wonder whats your global umask set to. and perhaps the user is not same when bitbake it running ?

The .h files will be in dev pkg in this case googletest-dev what happens if you add googletest to TOOLCHAIN_TARGET_TASK

yes if you use uninative ( which is default in poky) then it should be able to share across multiple build hosts. if you preserve PR server data then you should be good. sstate can be regenerated.

there is core-image-x11 which will be bareminimal and core-image-weston if you want to use wayland/weston based desktop. if you like XFCE for desktop then close meta-openembedded and add meta-oe and m

#dunfell

you should check the dependencies and ensure they are multilib safe sometimes dependencies could be hardcodes and cross the multilib boundaries accidentally > >

I think since kernel is 64bit it might be building some tools and packages to support kernel builds. Is there a specific need to not build 64bit userspace completely ? > >

there is system integration testing that happens on autobuilders which you can check reports for ptests are generic and one can add more to a package but usually you will see that its trying to run th

#systemd #yocto

minimal image is not ideal target as it is console only image perhaps use core-image-weston (wayland) or core-image-x11/core-image-sato ( X11 ) as starting point.

#yocto

find if docs can be disabled during build, and perhaps that will get you moving forward

#yocto

Yes, it lets you build custom Linux distribution and eases the way to add needed customization that one might require.

Usually these errors pop up when qemu usermode fails to run the needed programs during cross build. check the logs thoroughly and see if it leaves traces when executing update_icon_cache of any such i

#yocto

please use https://github.com/riscv/riscv-openjdk fork.

ensure that you are using same release branches for all layer repos generally RDEPENDS and RRECOMMENDS should be replaced with RDEPENDS_<pkgname> etc.

#kernel

Please try backporting this fix https://sourceware.org/git/?p=elfutils.git;a=commit;h=a01938d584b91e747167bb4b3f30ec300c4d6e43 if this is not enough then I think you just need to edit config/eu.am to

this class is provided by meta-oe layer. Make sure you have meta-oe layer in your bblayers.conf > >

#yocto

x11-* features is primarily to control what kind of x11 packages you want to include in image e.g. ./meta/recipes-sato/packagegroups/packagegroup-core-x11-sato.bb is pulled in when x11-sato is added t