AFAIK, there is no way to replace a do_install_append from another .bbappend; you'll have to modify the original.

If a recipe has a “do_install_append” can I create a bbappend file to do a “do_install_append_append” in order to change 1 line in that routine, or do I need to just replace the

Hi, Nicolas, Thank you for your reply. <nicolas.dechesne@...> wrote: But as far as I remember, previously I could have a single page view of a particular manual, for example "Development

Hi, Previously via https://docs.yoctoproject.org I was able to navigate to the single page view of a specific manual, for example "Reference Manual". But recently, something changed and it is only

Hi, Previously via https://docs.yoctoproject.org I was able to navigate to the single page view of a specific manual, for example "Reference Manual". But recently, something changed and it is only

The best way to centralise them would be to upstream them. Ross

related to something i asked a while back, i have a layer in front of me wherein dozens and dozens of .bbappend files exist for no other purpose than to contain the single line: BBCLASSEXTEND +=

merged. thanks

hey Vasyl, Can you please describe what you are doing in the webpage? It should still work. You need to select "All in one Mega manual" in the dropdown menu on the top left corner of the page. When

Awesome Konrad Thanks. That looks like it will do exactly what I need.

Signed-off-by: Khem Raj <raj.khem@...> --- recipes-support/libmpc/libmpc_%.bbappend | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-support/libmpc/libmpc_%.bbappend

Hi, I would recommend that you go for a systemd drop-in file [1]. That would be something like a small snippet placed to /etc/systemd/system/avahi-daemon.service.d/override.conf In that file place

Hi: I've been digging through meta/recipes-connectivity trying to figure out how I can override the avahi-daemon startup parameters. However I am not finding where the avahi-daemon.service file

Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- meta-cgl-common/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-cgl-common/conf/layer.conf

Thanks for mentioning that, it does sound like that is doing something we no longer should be doing now source_date_epoch is working in most packages properly. There are some files such as the rpm

perhaps bitbak meta-toolchain would suffice

Hi All, I need to deliver an SDK for arch64 but without Kernel headers that one can build Kernel modules with them. (/usr/include/linux/* , ...) I only need to deliver an SDK with toolchain and

Hey Manasa !! Long time, happy to hear from you. I hope you are doing well, Hi Vaijayanthi I took a look at hping3 and its one package thats not cross-compile friendly, So no wonder Vaijayanthi was

I have sussed out several behaviors of the image build having to do with reproducible builds. It seems like bitbake creates the rpm with the correct modification times per the reproducible_builds

it seems to be failing to find files on build host install and there were similar issues seen on chromium browswer long time ago which has been addressed in meta-browser. you might disable building