On Sat, Apr 25, 2020, at 3:38 PM, Bartłomiej Burdukiewicz wrote: > On Sat, Apr 25, 2020 at 06:46 AM, Khem Raj wrote:
>> On 4/24/20 8:01 AM, Bartłomiej Burdukiewicz wrote: > Mesa can be compiled >> with libva support, in order to avoid recursive > dependency between mesa >> and libva, virtual/mesa must be removed > from libva recipe. > > >> Signed-off-by: Bartłomiej Burdukiewicz [email protected] > >> --- > meta/recipes-graphics/libva/libva_2.6.1.bb | 2 +- > 1 file changed, 1 >> insertion(+), 1 deletion(-) > > diff --git >> a/meta/recipes-graphics/libva/libva_2.6.1.bb >> b/meta/recipes-graphics/libva/libva_2.6.1.bb > index 92cea83bc1..c1a441a18b >> 100644 > --- a/meta/recipes-graphics/libva/libva_2.6.1.bb > +++ >> b/meta/recipes-graphics/libva/libva_2.6.1.bb > @@ -23,7 +23,7 @@ >> SRC_URI[sha256sum] = >> "6c57eb642d828af2411aa38f55dc10111e8c98976dbab8fd62e4862940 > > >> UPSTREAM_CHECK_URI = "https://github.com/intel/libva/releases"; >> <https://github.com/intel/libva/releases%22> > > -DEPENDS = "libdrm >> virtual/mesa" > +DEPENDS = "libdrm" >> I am not sure how it will work with non-mesa graphics stacks. Or is it >> non-issue ? > It looks like libva is designed to work without mesa (or other graphical > stacks), since it's using libdrm to dispatch kernel calls. > https://en.wikipedia.org/wiki/Direct_Rendering_Manager#/media/File:DRM_architecture.svg > There is also ebuild in Gentoo for libva do not depend on mesa > (https://data.gpo.zugaina.org/gentoo/x11-libs/libva/libva-2.6.1.ebuild) or > other graphical stacks (like nvidia-drivers or etc.). > I'll provide more information about actual problem that is happening in > meta-kodi and it's related to this patch. > There is append that I created for meta-kodi, that is extending mesa with > libva and libvdpau capabilities: > https://github.com/dev-0x7C6/meta-kodi/blob/zeus/recipes-graphics/mesa/mesa_%25.bbappend > And this is current workaround for libva to avoid recursive dependency: > https://github.com/dev-0x7C6/meta-kodi/blob/zeus/recipes-graphics/libva/libva_%25.bbappend >>> inherit meson pkgconfig features_check > FYI, meta-amd also had to have appends to properly support va with AMD hardware via the mesa library. I think only Intel supplies accelerated video through DRM (without requiring mesa). Requiring virtual/mesa always seems to be redundant because libva recipe already required the OpenGL distro feature. I wanted to point out that libva can be built without enabling GLX support. But with_glx is set to auto and will use OpenGL if meson detects OpenGL being available and X11 is enabled. GLX support seems to enable some additional code for integration with the OpenGL stack.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137492): https://lists.openembedded.org/g/openembedded-core/message/137492 Mute This Topic: https://lists.openembedded.org/mt/73242971/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
