Open hoinmic opened 2 years ago
The .so should probably go into a library package. That could be used by modern SWUpdate which no longer needs static linking.
I meant the current naming cannot be processed properly by bitbake. I meant something like following customization is needed: libebgenv-${PV}*.so -> libebgenv.so.${PV}
Hi, I am trying to use EBG with swupdate 2022.05 on yocto and I am having a problem with swupdate not being able to find the shared library. It seems that the symlink libebgenv-0.10.so ->libebgenv.so.0 is not created. Can youl help me out fixing this? Thanks!
Unfortunately, I am currently only working with swupdate 2021.11.
Hi, I am building a yocto dunfell, swupdate tag 2022.05 (released a few days ago) with meta-efibootguard from mainline (commit 67311871755ca85c1b8a99bb371c6f7c16dfc7f0). It seems to me that no other branch addresses this. The problem is that /usr/lib/libebgenv-0.10.0.so is created, but it's missing a link to /usr/lib/libebgenv.so.0 required by swupdate 2022.05
https://github.com/siemens/meta-efibootguard/blob/17730b5bdf7467dca33c5e6a941b6206d9e1f661/recipes-bsp/efibootguard/efibootguard_0.10.bb#L48
I guess in the recipe the file "${libdir}/libebgenv-${PV}.so" could be deleted. Then bitbake would put the .so link in the dev package instead of installing on the target.