[Mesa-dev] [PATCH 1/2] configure.ac: enable building GLES1 and GLES2 by default

Emil Velikov emil.l.velikov at gmail.com
Thu May 28 05:07:29 PDT 2015


On 27/05/15 16:59, Matt Turner wrote:
> On Wed, May 27, 2015 at 4:53 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> On 27 May 2015 at 11:23, Dave Airlie <airlied at gmail.com> wrote:
>>>> Wow, I hadn't expected such a hateful comment on GLES1.
>>>>
>>>> Does anyone else want to convince me that GLES1 should burn in hell?
>>>
>>> So I dug around,
>>>
>>> commit 4c06853833996d990eb76b195ca5d6838c6f3d6b
>>> Author: Adam Jackson <ajax at redhat.com>
>>> Date:   Wed May 8 18:03:21 2013 -0400
>>>
>>>     Switch to Mesa master (pre 9.2)
>>>
>>>     - Fix llvmpipe on big-endian and enable llvmpipe everywhere
>>>     - Build vdpau drivers for r600/radeonsi/nouveau
>>>     - Enable hardware floating-point texture support
>>>     - Drop GLESv1, nothing's using it, let's not start
>>>
>>> So at least in Fedora 2 years ago, we realised there was no GLES1
>>> users in the distro,
>>> and we didn't want to encourage any.
>>>
>>> I suppose some users might exist outside the classic Linux distro
>>> world. i.e. android, embedded land.
>>>
>> At least three other distros have GLES1 - Arch, Debian and OpenSUSE.
>> So imho one should just leave the decision to depreciate/kill it off
>> to the distros ?
> 
> No one is suggesting deleting GLES1.
> 
Ack - I'm aware of that. I'm not sure which part of my statement led
came out as the opposite. If you can point me out as such that'll be
appreciated.

> I think distributions are going to inevitably ship things they have no
> reason to, regardless of our defaults, often because they don't know.
> The best we can do is guide their hands. If GLES1 is unused, we should
> note that in configure.ac to better communicate it to the
> distributions.
> 
No objection on the hand-holding, but the idea that Mesa knows which
distro does not ship/have GLES1 compatible software sounds a bit
strange. So I was pointing out that some (be that by mistake or not)
still have/use it.

At the end of the day, do as you please. The argument of "distro X
defaults to Y, so mesa should do the same", just seems strange to me.

Similar to Marek, I do wonder about the hostility towards GLES1. Sure it
is a bit old, and the API is not the most flexible/useful but there are
dozens (hundreds?) of projects that fit the criteria :)

-Emil


More information about the mesa-dev mailing list