Skip to contentSkip to conversation

Debugging dev-deps

DISCUSSION Matthias Schoepfer 3 participants 4 messages May 13, 2019 – May 14, 2019

lore
Share & tools
lore
#0 lore raw

Hi!

I am trying to write a recipe for a rather tricky component (that has plugins and stuff). Anyhow, I cannot get bitbake not to complain that <PACKAGENAME> rdepends on <PACKAGENAME>-dev. And if I INSANE_SKIP it, the -dev package will get installed. But I cannot figure out which file is responsible. I tried to ldd all installed files in <PACKAGENAME>, but could not get any results. Any hints on how to debug this further?!

Thanks and regards,

  Matthias

#1 lore raw
Quoted 6 lines · Matthias Schoepfer

I am trying to write a recipe for a rather tricky component (that has plugins and stuff). Anyhow, I cannot get bitbake not to complain that <PACKAGENAME> rdepends on <PACKAGENAME>-dev. And if I INSANE_SKIP it, the -dev package will get installed. But I cannot figure out which file is responsible. I tried to ldd all installed files in <PACKAGENAME>, but could not get any results. Any hints on how to debug this further?!

The problem is probably that the plugins are being shipped as /usr/lib/libpluginfoo.so, and so have the same names as development library symlinks which get packaged into PN-dev automatically. Alternatively unversioned libraries will also have the same issue.

Look at what files go into what package (using oe-pkgdata-util), and ensure that PN-dev only contains headers and the link-time symlinks. For example libfoo.so -> libfoo.so.1, libfoo.so should be in PN-dev and libfoo.so.1 should be in PN.

Ross

#2 lore raw

also read through
https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries

This might be helpful especially section under Non-versioned Libraries

Quoted 26 lines · Ross
Quoted 6 lines · Matthias Schoepfer

I am trying to write a recipe for a rather tricky component (that has plugins and stuff). Anyhow, I cannot get bitbake not to complain that <PACKAGENAME> rdepends on <PACKAGENAME>-dev. And if I INSANE_SKIP it, the -dev package will get installed. But I cannot figure out which file is responsible. I tried to ldd all installed files in <PACKAGENAME>, but could not get any results. Any hints on how to debug this further?!

The problem is probably that the plugins are being shipped as /usr/lib/libpluginfoo.so, and so have the same names as development library symlinks which get packaged into PN-dev automatically. Alternatively unversioned libraries will also have the same issue.

Look at what files go into what package (using oe-pkgdata-util), and ensure that PN-dev only contains headers and the link-time symlinks. For example libfoo.so -> libfoo.so.1, libfoo.so should be in PN-dev and libfoo.so.1 should be in PN.

Ross
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#3 lore raw
In reply to Burton, Ross

Hi Ross,

thanks for the hints, funnily enough it was .so symlinks that where in -dev and caused the dev-deps...

Regards,

    Matthias

Quoted 19 lines · Ross
Quoted 6 lines · Matthias Schoepfer

I am trying to write a recipe for a rather tricky component (that has plugins and stuff). Anyhow, I cannot get bitbake not to complain that <PACKAGENAME> rdepends on <PACKAGENAME>-dev. And if I INSANE_SKIP it, the -dev package will get installed. But I cannot figure out which file is responsible. I tried to ldd all installed files in <PACKAGENAME>, but could not get any results. Any hints on how to debug this further?!

The problem is probably that the plugins are being shipped as /usr/lib/libpluginfoo.so, and so have the same names as development library symlinks which get packaged into PN-dev automatically. Alternatively unversioned libraries will also have the same issue.

Look at what files go into what package (using oe-pkgdata-util), and ensure that PN-dev only contains headers and the link-time symlinks. For example libfoo.so -> libfoo.so.1, libfoo.so should be in PN-dev and libfoo.so.1 should be in PN.

Ross