Hi Prashanth, It depends exactly which package you're talking about. The superset of all licenses of all packages created by the gnutls recipe is GPLv3+ & LGPLv2.1+. This is also the default if the li

Salut Bastien, The `file` command on Linux (could be run on the host and not the target) will give you important info such as the architecture for which it was built. In that case, we would have detec

#yocto

Hi Marek, This seems wrong. **RDEPENDS** (dependency at runtime, on the target) on a **native** (for the host only) package does not make sense to me. I think we need more context (what are you trying

Hi Stefan, Your recipe can now be used in DEPENDS of other recipes with both "my-recipe" and "my-recipe-package". N.B.: please do not use underscore in recipe names, it can have weird consequences (be

#yocto

Hi Stefan, I think you meant PACKAGES and not PROVIDES here. If that is the case, then yes, congrats, you found the root cause :) Otherwise, I think there might be something worth debugging and maybe

#yocto

Hi Emily, You can create a patch for it. You can use devtool modify <your-recipe> and create the patch from there, you have access to the sources with that. devtool build <your-recipe> to check it bui

Hi Emily, I should have read more carefully, sorry. So... After googling a little bit I stumbled upon: https://askubuntu.com/a/486184 "The -mt suffix had been removed. The installed Boost libraries ar

Hi Emily, Ok so two things. Yes, I'd say you need python in PACKAGECONFIG for boost. However, it seems it's already part of the default value of PACKAGECONFIG, c.f. http://cgit.openembedded.org/openem

Hi JH, It was recently changed to libubootenv IIRC. Are you sure it was taken from u-boot git repo? In zeus you have both available if you have meta-swupdate layer but u-boot-fw-utils is still present

Hi Kent, inherit module should usually be enough in the recipe AFAICT. There might be some fixes to do in Makefiles but nothing crazy. c.f. https://www.yoctoproject.org/docs/current/mega-manual/mega-m

Hi Dmitri, I've had this before with a vendor layer. The culprit was the distro having some weird USERADDEXTENSION messing up with everything. How we found out what it was was by uncommenting: https:/

Hi JH, None. Or all of them, depends on how one sees it. You just create a directory in do_install of a recipe. You then make sure this directory is part of a package by checking it's in one of the re

Hi Philip, *Very* quick and vague answer as it's not something I'm doing right now. I can only give hints to where to look next. Have you had a look at INHERIT += "rm_work"? Should get rid of most of

#yocto

Hi JH, This function is not defined. So you look it up in the sources, find where it's defined. Is it in a file which is compiled/included somewhere? Is it surrounded by #ifdef? And by surrounded, I m

On Tue, Feb 04, 2020 at 04:32:34PM +0000, Ryan Harkin wrote: [...] > > Actually, it does work like this: > > export MACHINE=xyz > bitbake image > > But not like this: > > MACHINE=xyz bitbake image > >

Hi Ryan, It depends on what exactly does this recipe represent? A kernel module? In which case, you can put it in your machine configuration file under MACHINE_ESSENTIAL_EXTRA_RDEPENDS or RRECOMMENDS

Hi Ryan, You can make two machine configuration files. One with PREFERRED_VERSION_virtual/kernel = "4.9%" and the other with 4.19. They pick the correct machine when building, they should expect the c

Hi Ed, Please have a look at your mail formatting, I'm missing most new lines and it makes it hard to read your mail. You would need staticdev-pkgs in your EXTRA_IMAGE_FEATURES to have the static libr

Hi JH, I think you're looking for `git format-patch`. This creates a patch for the latest commit (HEAD). Take this .patch and add it to your SRC_URI in a bbappend. Also as Gabrielle said, U-Boot is ha

Hi Kent, Find the task which is doing some logic with the config fragments and disable it. Replace it by or add a new task which is taking your .config and putting it in ${S}. Kernel recipes are alway