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 HA
Well, I see your point. Thanks!
On Tue, Jul 30, 2024 at 8:10 AM Khem Raj wrote:
>
>
> On Mon, Jul 29, 2024 at 5:23 PM MOHAMMED HASSAN via lists.yoctoproject.org
> wrote:
>
>> Well, I seem to be facing issue with the bluez stack. Though it builds
>> well, functionality wise I think it doesn’t w
On Mon, Jul 29, 2024 at 5:23 PM MOHAMMED HASSAN via lists.yoctoproject.org
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
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 ar
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 HAS
