Hello Quentin,
Yes not uncommon setup except my prebuilt libraries don't match the initial
expectations:
1. The filename must have the version appended, for example: libbar.so.1.2.3.
(can be easily renamed by the way)
2. The library must have the ELF tag SONAME set to the major version of the
library, for example: libbar.so.1. (it has no SONAME at all and it's not
possible to have it, and not wanted to patch the library before using it to
build libfoo).
My customer don't want me to add the bar libraries in the rootfs. he ask me to
add only the foo libraries, for both architectures aarch64 and arm. Yes I have
bar libraries pre-compiled for both aarch64 and arm too. So this is lib32-bar
and bar.
>
> I assume that the automagic RDEPENDS got broken for lib32-foo and you are
> not seeing it because of INSANE_SKIP:${PN} += "file-rdeps"
> It's probably trying to locate a multilib lib32 package containing
> libbar.so but cannot find any and complains about it. The aarch64 package
> does find a package for libbar.so so it adds it automatically.
>
Interesting remark. Maybe I have to play with the INSANE_SKIP(s).
So the "file-rdeps" skip breaks the RDEPENDS on lib32-foo, which permit me to
not integrate lib32-bar in the rootfs (what I want), but it's maybe not working
with aarch64 ? Is there a "aarch64-file-rdeps" or similar (I don't think so)
that could help to break the RDEPENDS of my library foo on the library bar ?
Joel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62959): https://lists.yoctoproject.org/g/yocto/message/62959
Mute This Topic: https://lists.yoctoproject.org/mt/105558513/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
