I suspect the eSDK adds a workspace for the devtool and similar workflows so that piece may be normal and perhaps it was conflicting with your existing workspace? I have to admit I don't remember if

Richard,

I'm now wondering what happens if you remove   <my_home_dir>/poky/poky-build/workspace \ since I suspect your local workspace probably doesn't make sense in the eSDK? Could you try temporarily

Hello Khem, Doing "bitbake -e core-image-swupdate | grep ^INIT_MANAGER=" shows INIT_MANAGER="none". And "bitbake -e core-image-swupdate | grep ^DISTRO_FEATURES=" shows DISTRO_FEATURES="acl alsa argp

Richard,

Sorry, I'm getting confused here with earlier work Michael Ho did at BMW. The links here: https://lists.yoctoproject.org/g/yocto/message/52650 https://github.com/bmwcarit/meta-abicompat are the

That's true, this will require engagement from the community. Tool could take few iterations to perfect. Until then, I expect tool owner to be responsible for fixing these bugs. Once stability is

Thanks, I'm not seeing anything too odd there. I guess next we need to see the bblayers.conf that the code is building into the eSDK and compare it to your original conf/bblayer.conf. The generated

You're after our LTS to maintain ABI. In order to do that we need help, not just with patches generating some output, but in day to day running of the project, i.e. help comparing output before and

What would be the minimum acceptable solution with the least investment? in other words, do we have a list of requirements? Our team has posted a solution. BMW folks posted a solution. None of them

Richard,

I think its not that LTS itself but also upgrade from LTS to LTS or other newer versions, it wouuld be good to have this tool and prerhaps a list of API/ABI changes to help migration/upgrade to newer

I think core-image-swupdate.bb is adding sysvinit explicitly, please remove it from that.

thanks for patch. Can you create a PR on github please ?

Could you share what bitbake -e shows BBFILES as being set to? The variable history from that command for the variable may also be helpful.  There has to be something different to how you're setting

All, I've used the SDK in the past and want to start using the eSDK for my project. I'm on the dunfell branch. I'm trying to build the eSDK for my image by calling: bitbake <my_image_name> -c

Whilst there isn't a guarantee, it is something we're doing our best to ensure. Where there are security issues and we can't fix them as being backwards compatible, we reserve the right to break

<richard.purdie@...> wrote: I'd be interested in hearing about any cases where we've broken things! In general I don't take version upgrades (other than bug fix/cve fix only dot

<richard.purdie@...> wrote: Relatedly, somewhere I have a branch that uses libabigail to extract the library ABIs in an build. The next step was doing the comparison, but I never got

From: Aníbal Limón <limon.anibal@...> Gstreamer upgraded to 1.20 see, https://git.openembedded.org/openembedded-core/commit/?id=75891f361f3e9df9fc3e97c720a2ae57dda75888 Signed-off-by: