On Mon, Sep 02, 2013 at 12:22:18PM +0100, Richard Purdie wrote:
> On Sun, 2013-07-07 at 01:13 +0200, Martin Jansa wrote:
> > * when package contains some files matching "^.*\.so", but in directory
> > not default linker search paths (e.g. /opt/package/bundled-lib/libfoo.so)
> > don't register it as libfoo provider, because it's possible that there
> > is different package providing libfoo.so in ${libdir} and that would
> > be better shlib provider for other packages to depend on
> > * recipes providing libs intentionally in some other directory can
> > define own SHLIBSSEARCHDIRS value
> >
> > [YOCTO #4628]
> >
> > Signed-off-by: Martin Jansa <[email protected]>
> > ---
> > meta/classes/package.bbclass | 26 +++++++++++++++++++++++---
> > 1 file changed, 23 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> > index 6c3ca56..3713fd3 100644
> > --- a/meta/classes/package.bbclass
> > +++ b/meta/classes/package.bbclass
> > @@ -1307,6 +1307,9 @@ SHLIBSDIRS = "${@getshlibsdirs(d)}"
> > SHLIBSDIR =
> > "${TMPDIR}/pkgdata/${PACKAGE_ARCH}${TARGET_VENDOR}-${TARGET_OS}/shlibs"
> > SHLIBSWORKDIR = "${PKGDESTWORK}/shlibs"
> >
> > +# default search path when searching for shlibs provided by package
> > +SHLIBSSEARCHDIRS ?= "${baselib} ${libdir}"
> > +
> > python package_do_shlibs() {
> > import re, pipes
>
> Did you end up setting SHLIBSSEARCHDIRS for many recipes out of
> interest?No, but I was testing it only with world builds which won't cause any fatal error when something is missing in shlibs providers. Maybe I should revert it in my build and compare runtime deps after another build (I'll do this when jenkins server is free again). -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
