Current Dev Position: YP 3.3 M1 development Next Deadline: 7th December 2020 YP 3.3 M1 build Next Team Meetings: Bug Triage meeting Thursday Nov. 26th at 7:30am PDT

Hi Vijay Reading and following the section about "Writing a New Recipe" in the manual is probably a good starting

Hi, I'm new to the Yocto Project, trying to include my python application into the build. Can anyone guide me how to write a bitbake recipe .bb file or any example recipe would be helpful. Thank &

Thank you all, I appreciate the opportunity given to me to intern with the Yocto Project. I am excited about this internship and I look forward to working with you on my project. Sincerely, Dorinda.

Hi Michael, Use an anonymous python function that sets VERSION, e.g.: python __anonymous() { d.setVar('VERSION', find_version(d)) } as anonymous python functions are always executed during

Thank you all so much for having us. I learned so much about embedded linux and the Yocto Project in a very short while. I can't wait to start working with you and on my project. Cheers, Ida.

Yes SYSTEMD_AUTO_ENABLE_${PN} doesn't apply to systemd recipe core services as they are not installed as separate packages. But I got it working now. The default enable/disable service are defined in

Dear all, We are very excited to be part of the Outreachy program again for the December round this year, let me congratulate Ida and Dorinda for being accepted as interns for the next three

If you set BB_DONT_CACHE = "1" in the recipe, it will force the recipe to reparse each time. That should cause it to rerun find_version and then change hash when the value changes. Its how SRCREV =

I do not want do_compile to run again, it rebuilds the whole image. What is the best way to always run find_version?

It don't see anything in the layer index: https://layers.openembedded.org/layerindex/branch/master/recipes/?q=mtree but the source has a configure file: (Ubuntu: apt-get source mtree-netbsd) so

The service is deployed with standard systemd package, which doesn't have that set as far as I see it (no SYSTEMD_AUTO_ENABLE_${PN} in the latest recipe revision) I think, after browsing through the

I think you need to set SYSTEMD_AUTO_ENABLE = “disable” (actually any value other than “enable”) in your bbappend. (It looks like SYSTEMD_AUTO_ENABLE_${PN} is intended to work too, but I

Hi, I would like to have systemd-timesyncd.service as part of an image but have it disabled by default. Right now it is enabled by default which causes some issues. I've tried

colleague wants to know if there is something available in an OE/YP layer equivalent to mtree: https://linux.die.net/man/8/mtree i'm looking at a few possibilities right now but nothing seems

please send a patch to make to correct the situation. -armin

Thanks, Khem. Yes, I am. I actually discovered what the problem was: I built my system for 64-bit but Broadcom's proprietary libraries are 32-bit. I switched the system to 32-bit and now gst-inspect

Ok - I understand now. Thanks for the explanation. Charlie

<charles.davies@...> wrote: This is correct. When at least one (binary) package is needed from a recipe, then the recipe is built, and all the resulting packages are built. So when you

Hi All, I am seeing some behaviour when creating my own packagegroups which I do not quite understand. Using the example from the mega-manual: DESCRIPTION = "My Custom Package Groups" inherit