Hi, Don't know if it works but was always wondering if adding PACKAGE_EXCLUDE = "connman" would be a way to know for sure at least one recipe that is "adding" connman to the image exists (and this als

Hi Bhavya, Your S = "${WORKDIR}" is probably wrong then. Is there only a directory "at the root" of the tarball? I mean if you untar it, do you get one directory where all your source code is? In that

#yocto

Hi Bhavya, SRC_URI = "file://gsm-${PV}.tar.gz \ file://license" or SRC_URI = "file://gsm-${PV}.tar.gz" SRC_URI += "file://license" Quentin

#yocto

Hi, I also see that there's only a kernel recipe. IIRC, kirkwood devices are supported in upstream linux, so you're probably fine using linux-yocto, copy paste and slightly modify the machine configur

#yocto

Hi Scott, IMAGE_INSTALL is the way to go. I recommend spending some time on watching https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj Here you'll learn that you shouldn't reall

Hi Pankaj, Update your dunfell branch (should be at commit c253fd28ad26b4996666b0794dfee1d59c14e3ca) Quentin

Hi Scott, Up till there, this discussion would probably fit some kernel communities more than the Yocto one. A few things though: - Bear in mind that using bitbake -c menuconfig virtual/kernel, the ch

#yocto #linux

Hi, What about: pkg_postinst_ontarget_${PN}() { : } in your bbappend? This should effectively override the task from a bbappend (except if there are _append for the task). Can't comment on this being

#yocto

Hi, IIUC, SSTATE_MIRRORS is just a way to prepopulate your local sstate-cache. So you'd need to have SSTATE_MIRRORS="" but also change SSTATE_DIR to some path where no sstate-cache is so that the loca

Hi Gary, I'm not sure setup.py is supported for the project as it's empty? So distutils does not look correct to me. You have a makefile (inherit no classes, that;s the default) or Cmakelists (inherit

#yocto

Hi Pankaj, packagegroup-core-x11-server is a recipe (well, both a recipe and a package) not a feature. If you want to add packagegroup-core-x11-server package to your image, you need to add it to IMAG

#yocto

Hi Pankaj, Missing x11 in DISTRO_FEATURES in your distro. http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb?h=master#n12 (I also

#yocto

Hi Pankaj,

#yocto

bitbake rrdtool -e and look for the line starting with PACKAGECONFIG. CHeck it's set to what you want, if not, look the lines above to understand why it's not set "correctly". Quentin

Hi, You have probably added core-image-sato to DEPENDS which is incorrect. You can't add an image recipe as a dependency. Quentin

#raspberrypi #yocto

Hi Stephan, Libraries and binaries are stripped of the debug symbols before adding them to the "normal" package. The version with the debug symbols are usually in the -dbg package of your recipe. You

#devtool

Hi Tomek, Because there is a misunderstanding on how _<override> works :) KERNEL_MODULE_AUTOLOAD_velismate += "A" KERNEL_MODULE_AUTOLOAD += "B" does not mean that you add A in case of velismate machin

Hi, _append in most cases require a leading space, i.e. you want: DISTRO_FEATURES_append = " pam" Let us know if that fixes it. Quentin

#yocto

Hi Damien, It is? https://git.busybox.net/busybox/tree/findutils/find.c#n206 You need to enable it in busybox config (you can use config fragments IIRC). layers.openembedded.org is your friend. For ex

Hi Ayoub, BBPATH[1] is what's used to locate bbclasses. It's defined in your conf/layer.conf. You can either make sure your layer is parsed before the one having the original systemd.bbclass (in BBLAY