I'd suggest you rebase your setup to master branches of all involved yocto layers. If you're not shipping a product, being on top of master is really a better option, as you'll get newest software, and can make more disruptive improvements to layers.
Alex On Tue, 30 Jul 2024 at 02:23, MOHAMMED HASSAN <hassanchatta...@gmail.com> wrote: > > Well, I seem to be facing issue with the bluez stack. Though it builds well, > functionality wise I think it doesn’t work as intended. So I wanted to try > building it on the board using the source code. Now the source code wants > glib-2 2.8 . > > Also, on a second thought how do you guys work your way around in case a > particular package is outdated? Really curious! > > Thanks > > On Tue, 30 Jul 2024 at 12:03 AM, Alexander Kanavin <alex.kana...@gmail.com> > wrote: >> >> You can try, but this is likely to unravel into a mass scale upgrade >> of half of oe-core recipes, and you're on your own trying to make it >> work. I would suggest simply moving to a tagged master milestone >> rather. >> >> Where is the requirement coming from? >> >> Alex >> >> On Mon, 29 Jul 2024 at 06:46, MOHAMMED HASSAN via >> lists.yoctoproject.org >> <hassanchattarki=gmail....@lists.yoctoproject.org> wrote: >> > >> > Hi guys, >> > I have kirkstone SDK with me that supports glib-2.0 version 2.70. I >> > currently require version 2.80 which I noticed is available in the main >> > branch of git. Do you think pulling the recipes and manually replacing the >> > file will resolve my issue. Or any other good methods I can try? >> > >> > Thanks >> > Hassan >> > >> > >> >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63601): https://lists.yoctoproject.org/g/yocto/message/63601 Mute This Topic: https://lists.yoctoproject.org/mt/107603886/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
