On 6 September 2012 14:25, Koen Kooi <[email protected]> wrote: > It's not automatic, but you can do something like this: > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=23b02134 > > That recipe ships multiple copies of the libraries to account for different > silicon revisions (the shader compiler will offload different things to the > CPU), but we don't want the shlibs code to pickup the copies. So for mesa you > can do: > > PRIVATE_LIBS_${PN}-dri = "libGL.so" > RPROVIDES_${PN}-dri = $magic_python_function(PACKAGE_CONFIG, > sometthing, something, libgl) > > And in the recipes that link to a GL lib you do: > > RDEPENDS_${PN} = "libGL"
Ah, interesting. I'm not entirely keen on the manual dependencies but that's certainly a step in the right direction. If automatic replacement dependencies were added to bitbake, how would you implement them? In Debian, libgl1-mesa installs a libgl1-mesa-glx.shlibs file with this contents: libGL 1 libgl1-mesa-glx | libgl1 "when linking to libGL.so, use the dependency 'libgl1-mesa-glx | libg1". All packages which contain libgl.so.1 have Provides: libgl1, so they are interchangable. Some way of expressing that in the bitbake recipe would be great. Ross _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
