On Mon, 2014-03-24 at 15:22 +0100, Steffen Sledz wrote: > On 24.03.2014 13:53, Richard Purdie wrote: > > On Mon, 2014-03-24 at 13:49 +0100, Steffen Sledz wrote: > >> On 24.03.2014 13:35, Richard Purdie wrote: > >>> On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote: > > debian.bbclass (debian package naming) which I believe in turn is > > derived from the actual library version. > > > > Its a class specific implementation so you can't depend on it in version > > information though. > > But where does it come from? A bb variable?
Read debian.bbclass. It does objdump -p and looks at the SONAME in the output. > > > I still think your only solution here is to inject a real version into > > PV... > > I tried this: > > change libfoo recipe to PV = "1.0+gitr${SRCPV}" > leads to libfoo0_1.0+gitr102+someotherhash....ipk > > then > > change app recipe to DEPENDS = "... libfoo-1.0 ..." > leads to: "ERROR: Nothing PROVIDES 'libfoo-1.0'" :( > > change app recipe to DEPENDS = "... libfoo0-1.0 ..." > leads to: "ERROR: Nothing PROVIDES 'libfoo0-1.0'" :( > > change app recipe to DEPENDS = "... libfoo0_1.0 ..." > leads to: "ERROR: Nothing PROVIDES 'libfoo0_1.0'" :( > > Where's the mistake? You'd need to do RDEPENDS_xxxx = "libfoo (>=1.0)" Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core