public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Vincent Davis Jr" <vince@underview.tech>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libglvnd: add new recipe libglvnd v1.5.0
Date: Sun, 23 Oct 2022 10:05:54 -0700	[thread overview]
Message-ID: <1878.1666544754793887571@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj__oO_F=t3DZDupCwFi8L_Q8FEZG=p8+iA48A_UY4xzuQ@mail.gmail.com>

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

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

[-- Attachment #2: Type: text/html, Size: 809 bytes --]

  reply	other threads:[~2022-10-23 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 17:10 [PATCH] libglvnd: add new recipe libglvnd v1.5.0 Vincent Davis Jr
2022-10-22 19:05 ` [OE-core] " Alexander Kanavin
2022-10-23 17:05   ` Vincent Davis Jr [this message]
2022-10-23 17:19     ` Alexander Kanavin
2022-10-23 17:42       ` Vincent Davis Jr

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=1878.1666544754793887571@lists.openembedded.org \
    --to=vince@underview.tech \
    --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