Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] libdrm: allow to build native and nativesdk
Date: Tue, 10 Jul 2018 11:49:36 +0200	[thread overview]
Message-ID: <20180710094936.GB1825@jama> (raw)
In-Reply-To: <05aaa19a3bf9bcf837150745d1ee17deaa41304f.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

On Tue, Jul 10, 2018 at 09:45:45AM +0100, Richard Purdie wrote:
> Normally I don't mind native/nativesdk variants but libdrm starts to
> worry me as its a short step away from mesa and when we've tried native
> or nativesdk versions in the past its been a nightmare, particularly
> around GL.
> 
> Could you explain a little more about why we need libdrm-native?

It's for mesa and nativesdk-mesa indeed and qemu-native with spice,
virglrenderer and opengl support enabled.

http://lists.openembedded.org/pipermail/openembedded-core/2017-September/142349.html

> On Tue, 2018-07-10 at 08:07 +0000, Martin Jansa wrote:
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> >  meta/recipes-graphics/drm/libdrm_2.4.92.bb | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/meta/recipes-graphics/drm/libdrm_2.4.92.bb
> > b/meta/recipes-graphics/drm/libdrm_2.4.92.bb
> > index 1526553254..b4d06d19a6 100644
> > --- a/meta/recipes-graphics/drm/libdrm_2.4.92.bb
> > +++ b/meta/recipes-graphics/drm/libdrm_2.4.92.bb
> > @@ -56,3 +56,5 @@ FILES_${PN}-kms = "${libdir}/libkms*.so.*"
> >  FILES_${PN}-freedreno = "${libdir}/libdrm_freedreno.so.*"
> >  FILES_${PN}-amdgpu = "${libdir}/libdrm_amdgpu.so.*"
> >  FILES_${PN}-etnaviv = "${libdir}/libdrm_etnaviv.so.*"
> > +
> > +BBCLASSEXTEND = "native nativesdk"
> > -- 
> > 2.17.1
> > 

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2018-07-10  9:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  8:07 [PATCH 1/2] libdrm: Add PACKAGECONFIG support for all meson options Martin Jansa
2018-07-10  8:07 ` [PATCH 2/2] libdrm: allow to build native and nativesdk Martin Jansa
2018-07-10  8:45   ` Richard Purdie
2018-07-10  9:49     ` Martin Jansa [this message]
2018-07-10 10:35       ` Burton, Ross
2018-07-10  9:41 ` [PATCH 1/2] libdrm: Add PACKAGECONFIG support for all meson options Burton, Ross
2018-07-10  9:52   ` Martin Jansa
2018-07-10 10:18     ` Burton, Ross

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=20180710094936.GB1825@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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