libglvnd: add new recipe libglvnd v1.5.0

Signed-off-by: Vincent Davis Jr <vince@underview.tech>
---
 .../libglvnd/libglvnd_1.5.0.bb                | 30 +++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 meta/recipes-graphics/libglvnd/libglvnd_1.5.0.bb

Any new recipe needs to be justified for inclusion in core. The criteria are:

- is this something that fulfils a significant, broadly applicable
embedded linux use case or developer workflow?
- is this a dependency of something else in core that would enable the
previous point?

Alex

On Sat, 22 Oct 2022 at 19:13, Vincent Davis Jr <vince@underview.tech> wrote:
>
> Signed-off-by: Vincent Davis Jr <vince@underview.tech>
> ---
>  .../libglvnd/libglvnd_1.5.0.bb                | 30 +++++++++++++++++++
>  1 file changed, 30 insertions(+)
>  create mode 100644 meta/recipes-graphics/libglvnd/libglvnd_1.5.0.bb
>
> diff --git a/meta/recipes-graphics/libglvnd/libglvnd_1.5.0.bb b/meta/recipes-graphics/libglvnd/libglvnd_1.5.0.bb
> new file mode 100644
> index 0000000000..b92bad46e0
> --- /dev/null
> +++ b/meta/recipes-graphics/libglvnd/libglvnd_1.5.0.bb
> @@ -0,0 +1,30 @@
> +DESCRIPTION = "libglvnd is a vendor-neutral dispatch layer for arbitrating \
> +OpenGL API calls between multiple vendors."
> +HOMEPAGE = "https://gitlab.freedesktop.org/glvnd/libglvnd"
> +LICENSE = "MIT & BSD-1-Clause & BSD-3-Clause & GPL-3.0-with-autoconf-exception"
> +LIC_FILES_CHKSUM = "file://README.md;beginline=323;md5=7ac5f0111f648b92fe5427efeb08e8c4"
> +
> +SRC_URI = "git://git@gitlab.freedesktop.org/glvnd/libglvnd.git;protocol=https;branch=master"
> +
> +# v1.5.0 tag
> +SRCREV = "c7cdf0cc4395b57563294d1f340b6bb1b95366a0"
> +
> +REQUIRED_DISTRO_FEATURES = "opengl"
> +
> +inherit meson pkgconfig features_check
> +
> +S = "${WORKDIR}/git"
> +
> +PACKAGECONFIG ?= "\
> +  ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11', '', d)} \
> +  ${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'egl gles1 gles2', '', d)} \
> +  ${@bb.utils.contains('DISTRO_FEATURES', 'opengl x11', 'glx', '', d)} \
> +  "
> +
> +PACKAGECONFIG[x11] = "-Dx11=enabled,-Dx11=disabled,libx11 libxext xorgproto"
> +PACKAGECONFIG[glx] = "-Dglx=enabled,-Dglx=disabled,libx11 libxext xorgproto"
> +PACKAGECONFIG[egl] = "-Degl=true,-Degl=false,"
> +PACKAGECONFIG[gles1] = "-Dgles1=true,-Dgles1=false,"
> +PACKAGECONFIG[gles2] = "-Dgles2=true,-Dgles2=false,"
> +
> +BBCLASSEXTEND = "native nativesdk"
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#172062): https://lists.openembedded.org/g/openembedded-core/message/172062
> Mute This Topic: https://lists.openembedded.org/mt/94500417/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Okay, yes this is an optional dependency of mesa. This recipe will allow for glvnd support in mesa.
Thus, giving access to the GLX window-system API library and related libraries, mesa will build
libGLX_mesa.so.*.* and libEGL_mesa.so.*.* when added. There may be applications that require
direct access to the GLX window-system API library in order to build/execute. This will allow for
multiple layers to have generic support for libraries in libglvnd (GLX window-system API library, etc...)
without needing to implement their own version of the libglvnd recipe.

Question, since the goal is to support glvnd in mesa.
Should I be creating a patch series for this or just leave it as individual patches?

Also, I'll update commit message with above response

I believe the glvnd recipe should be going to
meta-openembedded/meta-oe/recipes-graphics/, but any needed changes to
mesa recipe should be done here, as long as glvnd support is off by
default.

Alex

On Sun, 23 Oct 2022 at 19:05, Vincent Davis Jr <vince@underview.tech> wrote:
>
> Okay, yes this is an optional dependency of mesa. This recipe will allow for glvnd support in mesa.
> Thus, giving access to the GLX window-system API library and related libraries, mesa will build
> libGLX_mesa.so.*.* and libEGL_mesa.so.*.* when added. There may be applications that require
> direct access to the GLX window-system API library in order to build/execute. This will allow for
> multiple layers to have generic support for libraries in libglvnd (GLX window-system API library, etc...)
> without needing to implement their own version of the libglvnd recipe.
>
> Question, since the goal is to support glvnd in mesa.
> Should I be creating a patch series for this or just leave it as individual patches?
>
> Also, I'll update commit message with above response
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#172069): https://lists.openembedded.org/g/openembedded-core/message/172069
> Mute This Topic: https://lists.openembedded.org/mt/94500417/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

okay will do :)