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

Hi JH, /bin/ls -la /bin/busy* ? Maybe something is messing with the PATH environment variable. Or something is removing the symlinks from some binaries to busybox. IIRC, UBIFS is safe from power cycle

Hi Richard, Some packages are pulled as runtime dependencies (RDEPENDS from a package that is installed, or via the auto-RDEPENDS mechanism which detects if a package is a provider of a shlib required

#yocto

Hi Andy, I'm curious if subpath can be the path to a file directly and not a directory, in which case that might work good enough. Interesting one, thanks for telling me :) I'd add a task between do_f

Hi Andy, I unfortunately don't have experience with git lfs. I'm thinking about the subpath argument to SRC_URI git fetcher. https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-

Hi Tuomas, Please explain what you're doing exactly, maybe even the content of your bbappend and/or the original recipe and what you're expecting to happen, your description is too vague. FYI, variabl

Hi, I'm currently having issues with that on Thud though. We have a few python scripts in there and changes to those are not reflected in Yocto and do not trigger a rebuild. We have a meta/lib/mypytho

Hi Andy, Have a look at the paths traversed by Yocto to find your asound.state in log.do_fetch in the WORKDIR. You'll have the following: DEBUG: Searching for asound.state in paths: The first path to

Hi Ed, I think you might be missing `ENABLE_UART = "1"`. We have it in local.conf but I think you should be able to put it in your machine conf file or in your distro conf file if you can't modify loc