Will have change for placing /usr/share/glvnd/egl_vendor.d/50_mesa.json into
FILES:libegl-mesa next patch.
To answer first question. I'd say yes, there may be multiple recipes that
contain an implementation of libGLX_VENDOR library
(libGLX_mesa.so, libGLX_nvidia.so, etc...). Although mesa recipe
> +PREFERRED_PROVIDER_virtual/libglx ?= "mesa"
Is there a real need for another preferred provider here?
> + if ${@bb.utils.contains('PACKAGECONFIG', 'egl', 'true', 'false', d)} && [
> -f ${D}${includedir}/EGL/eglplatform.h ]; then
Might as well just do the test, and not bother looking at PACK
Hello,
Is there any status on merging this?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173666):
https://lists.openembedded.org/g/openembedded-core/message/173666
Mute This Topic: https://lists.openembedded.org/mt/94584118/21656
Group Owner: op
Hi,
Are there any autobuilder updates on this?
Know last patch I didn't realize I wasn't packaging the EGL .so in development
package.
FILES:libegl-mesa-dev = "${libdir}/libEGL*.so.*..."
Patch updates to
FILES:libegl-mesa-dev = "${libdir}/libEGL*.* ..."
-=-=-=-=-=-=-=-=-=-=-=-
Links: You rece
Allows mesa to be built with glvnd support.
Thus, creates libEGL_mesa.so* and libGLX_mesa.so*
libraries meant to coexist with vendor neutral
dispatch libraries from libglvnd.
Signed-off-by: Vincent Davis Jr
---
.../conf/distro/include/default-providers.inc | 1 +
meta/recipes-graphics/mesa/mesa
