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? Cheers, Richard On Tue, 2018-07-10 at 08:07 +0000, Martin Jansa wrote: > Signed-off-by: Martin Jansa <[email protected]> > --- > 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 > -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
