All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Mark Hatle <mark.hatle@kernel.crashing.org>
Cc: Denys Dmytriyenko <denis@denix.org>,
	"Burton, Ross" <ross.burton@intel.com>,
	 OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] mesa-gl: The purpose of mesa-gl is to provide for X11 usage
Date: Wed, 25 Mar 2020 20:04:19 +0100	[thread overview]
Message-ID: <CANNYZj_s6yG2qRnEMv_PrFc6ut2mOfJFNFpBd4EzdhUHe8Xxyw@mail.gmail.com> (raw)
In-Reply-To: <11151.149.199.62.130.1585161676.squirrel@gate.crashing.org>

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

To be honest, I would just take the entire recipe out. It's causing trouble
during updates, isn't being tested neither for builds nor at runtime, and
is supposed to provide some specific configuration which as this discussion
makes clear, nobody seems to quite understand.

Alex

On Wed, 25 Mar 2020 at 19:42, Mark Hatle <mark.hatle@kernel.crashing.org>
wrote:

> > On Wed, Mar 25, 2020 at 01:14:47PM -0500, Mark Hatle wrote:
> >> Trying to build mesa-gl without X11 enabled, results in numerous errors
> >> about being incorrectly configured, such as:
> >>
> >>   ERROR: Problem encountered: building dri drivers require at least one
> >> windowing system or classic osmesa
> >>
> >> After consulting with the author of this recipe, it was clear that it
> >> was only intended for the X11 use-case, so requring X11 should avoid the
> >> error message above.
> >
> > Hmm. That's not good. There are embedded devices that provide EGL/GLES
> > support
> > through own stack, but fall back on MESA for full desktop GL support.
> > That's
> > been working to some extent even with Wayland and w/o X11. With your
> > change
> > that won't be possible any more...
>
>
> Have you tried any of these?  This hasn't been working since Zeus with an
> external libmali and non-X11 configuration.  It returns the error listed
> in the commit message "ERROR: Problem encountered: building dri drivers
> require at least one windowing system or classic osmesa" during
> configuration.
>
> Ross and I talked about it and he said this was specific to X11
> implementation and wasn't meant to work for other implementations.
> (fbdev/QT/etc.)
>
> If Wayland is supposed to work, then someone needs to go in and adjust the
> configuration to also support Wayland.  I don't have any Wayland systems
> to even know what the right configuration COULD be.
>
> The specific configuration I'm running has "OpenGL" in the DISTRO_FEATURE,
> but does NOT have X11 or Wayland".
>
> DISTRO_FEATURES_append = " opengl"
> DISTRO_FEATURES_remove = "x11 wayland"
>
> --Mark
>
> > --
> > Denys
> >
> >
> >> Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
> >> ---
> >>  meta/recipes-graphics/mesa/mesa-gl_20.0.1.bb | 6 ++++--
> >>  1 file changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/meta/recipes-graphics/mesa/mesa-gl_20.0.1.bb
> >> b/meta/recipes-graphics/mesa/mesa-gl_20.0.1.bb
> >> index d4b1c1c454..5674c6b1fe 100644
> >> --- a/meta/recipes-graphics/mesa/mesa-gl_20.0.1.bb
> >> +++ b/meta/recipes-graphics/mesa/mesa-gl_20.0.1.bb
> >> @@ -6,5 +6,7 @@ PROVIDES = "virtual/libgl virtual/mesa"
> >>
> >>  S = "${WORKDIR}/mesa-${PV}"
> >>
> >> -PACKAGECONFIG ??= "opengl dri ${@bb.utils.filter('DISTRO_FEATURES',
> >> 'x11', d)}"
> >> -PACKAGECONFIG_class-target = "opengl dri
> >> ${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}"
> >> +REQUIRED_DISTRO_FEATURE = "x11"
> >> +
> >> +PACKAGECONFIG ??= "opengl dri x11"
> >> +PACKAGECONFIG_class-target = "opengl dri x11"
> >> --
> >> 2.17.1
> >>
> >
> >>
> >
>
> 
>

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

  reply	other threads:[~2020-03-25 19:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 18:14 [PATCH] mesa-gl: The purpose of mesa-gl is to provide for X11 usage Mark Hatle
2020-03-25 18:21 ` [OE-core] " Denys Dmytriyenko
2020-03-25 18:41   ` Mark Hatle
2020-03-25 19:04     ` Alexander Kanavin [this message]
2020-03-25 19:27       ` Mark Hatle
2020-03-26 13:11         ` Adrian Bunk
2020-03-26 14:15           ` Mark Hatle
     [not found]   ` <15FFA02F5F44ED82.23217@lists.openembedded.org>
2020-03-25 19:04     ` Mark Hatle
2020-03-25 20:02 ` Andrey Zhizhikin
2020-03-25 20:35   ` Mark Hatle
2020-03-25 21:37     ` Andrey Zhizhikin
2020-03-25 21:48       ` Denys Dmytriyenko
2020-03-25 21:58 ` Otavio Salvador
2020-03-30 12:07   ` Ross Burton

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=CANNYZj_s6yG2qRnEMv_PrFc6ut2mOfJFNFpBd4EzdhUHe8Xxyw@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=denis@denix.org \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.