libcansocket: Weird issue with pkgsplit
Tuomas Huuki <tuomas.huuki@...>
Hello all,
I have an interesting situation with libcansocket and bitbake that I cannot wrap my head around. For some reason, the packages are being split up somewhat strangely and I cannot figure out why. First of all, the recipe used is: https://github.com/openembedded/meta-openembedded/blob/9a0de2779b9b31f134ffe19388b5b9b37bb6450e/meta-oe/recipes-extended/socketcan/libsocketcan_0.0.11.bb So no strange things there. Additionally, looking at the built items: ../build/tmp/work/aarch64-poky-linux/libsocketcan/0.0.11-r0/image/usr/lib$ ls -lah libsocketcan* lrwxrwxrwx 1 tuomas tuomas 21 maali 18 10:38 libsocketcan.so -> libsocketcan.so.2.3.0 lrwxrwxrwx 1 tuomas tuomas 21 maali 18 10:38 libsocketcan.so.2 -> libsocketcan.so.2.3.0 -rwxr-xr-x 1 tuomas tuomas 58K maali 18 10:38 libsocketcan.so.2.3.0 All looks good at this point. Now, when I deploy the image, the first link is missing. $ oe-pkgdata-util list-pkg-files libsocketcan I have been through the logs and cannot figure out why. FILES_${PN} += "${libdir}/*.so"
But no luck. Looking at pkgdata/runtime/libsocketcan I notice: FILES_libsocketcan: /usr/bin/* /usr/sbin/* /usr/libexec/* /usr/lib/lib*.so.* /usr/lib/*.soBut again this is missing the .so for some reason. Additionally, I noticed that for some reason the package is renamed to libsocketcan2 (log.do_package). Why? Could this be part of the issue? > NOTE: debian: renaming libsocketcan to libsocketcan2 How does pkgconfig decide how to split packages. Can anyone point me to proper documentation? Thanks! Tuomas Huuki Crosscontrol Oy
|
|