> 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.

With the abomination that is libmali (and similar), it is still needed. 
It's the only way to support GL on a primarily GLES compatible system.

The problem is the way they do this seems to be a custom version of
libdrm, which then conflicts with the mesa version.  Thus the issues.

I'm happy to continue testing my particular needs now and the future (thus
the patch against master.)

What we absolutely don't want is a different version of this for every
system that has a custom graphics chip in it.  That would be a far larger
nightmare than what is currently implemented.  The key to this is to come
to an agreement on what should work and how it should be configured.  As
of right now, the only working configuration I can find is X11.

--Mark

> Alex
>
> On Wed, 25 Mar 2020 at 19:42, Mark Hatle <[email protected]>
> 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 <[email protected]>
>> >> ---
>> >>  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
>> >>
>> >
>> >>
>> >
>>
>> 
>>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#136703): 
https://lists.openembedded.org/g/openembedded-core/message/136703
Mute This Topic: https://lists.openembedded.org/mt/72547327/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to