You just need to switch all the layers to the needed branch and run the build, and see what happens. It's impossible to predict that until the build runs and fails in some way, but when it does fail, we can offer guidance, or you can look it up in migration guides first perhaps.
I'm not sure where kirkstone went in meta-xilinx, but you can just use mickledore. Alex On Thu, 10 Aug 2023 at 12:51, msenturk <senturkmurat1...@gmail.com> wrote: > > I looked for Kirkstone but there is only a kirkstone-next layer for > meta-xilinx repository: > https://github.com/Xilinx/meta-xilinx/tree/kirkstone-next. I actually don't > understand what the difference is between these normal and -next branches. My > guess is they create them for the uncompleted code. Once they complete the > coding, they publish with normal branch name such as "kirkstone". Therefore, > I am planning to use Mickledore: > https://github.com/Xilinx/meta-xilinx/tree/mickledore. Alexander Kanavin's > explanation is also something I'll care. Can I migrate from Gatesgarth to > Mickledore directly or do I need to migrate those version one by one? I read > some of these migration guides but kinda didn't understand to be honest. They > seem more like giving information about what they changed with the new > version instead of what you have to change to migrate this version. Besides > of switching branches, do I need to download host packages: > https://docs.yoctoproject.org/4.2.2/brief-yoctoprojectqs/index.html#build-host-packages. > Thank you. > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60773): https://lists.yoctoproject.org/g/yocto/message/60773 Mute This Topic: https://lists.yoctoproject.org/mt/100525085/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
