public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"bartlomiej.burdukiewicz@gmail.com"
	<bartlomiej.burdukiewicz@gmail.com>
Subject: Re: [OE-core] [meta-oe][PATCH] libva: Removed virtual/mesa dependency
Date: Sun, 26 Apr 2020 04:23:57 +0000	[thread overview]
Message-ID: <e5e73ac7edc8c2695ca5dd0d31e9d800480a4e8c.camel@intel.com> (raw)
In-Reply-To: <28192.1587843536617759309@lists.openembedded.org>

On Sat, 2020-04-25 at 12:38 -0700, 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
> > bartlomiej.burdukiewicz@gmail.com > --- > 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" > >
> > -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 see a DEPEND on opengl there which is what glx backend in libva
expects:

https://github.com/intel/libva/blob/master/meson.build#L95

Just removing the dependency will force glx backend to not be built. Is
there software out there that expects libva-glx to be present?

Thanks,

Anuj

  parent reply	other threads:[~2020-04-26  4:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 15:01 [meta-oe][PATCH] libva: Removed virtual/mesa dependency bartlomiej.burdukiewicz
2020-04-25  4:46 ` [OE-core] " Khem Raj
2020-04-25 19:38   ` Bartłomiej Burdukiewicz
2020-04-25 23:03     ` [OE-core] " Fred Baksik
2020-04-26  4:23     ` Anuj Mittal [this message]
2020-04-27 23:09       ` Bartłomiej Burdukiewicz
2020-04-28  8:47         ` Richard Purdie
2020-04-29 11:50           ` Bartłomiej Burdukiewicz
2020-05-06 12:41 ` Zoltan Boszormenyi
2020-05-07 11:25   ` Bartłomiej Burdukiewicz
2020-05-07 11:48   ` Richard Purdie
2020-05-07 12:47     ` Zoltan Boszormenyi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5e73ac7edc8c2695ca5dd0d31e9d800480a4e8c.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=bartlomiej.burdukiewicz@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox