Scott Talbert

Seems like a reasonable thing to do. Any thoughts on what should happen if EGL is < 1.5 at runtime? Warning? Assert?

Agreed, adding this error message might be only slightly more helpful than the `undefined symbol` errors the original user saw. Yes, the ideal answer is to be able to pick...

Yes, indeed, that was the approach we discussed and that I was attempting. However, it's a bit more complicated in that `wxGLContext` needs to be modified in a similar way,...

I don't have immediate plans to work on it - so if you've got the time and interest to work on it, feel free.

@Steelskin, this would be great, especially the runtime selection of GLX vs EGL. A delegate approach might be OK (would need to know more details), but keep in mind that...

> > To be honest, we could probably support older versions of EGL, though. I just picked the latest when I implemented the original EGL support because it was new...

> I can't fully follow the proposal here. Why does this need more complicated then the default backend being GLX, which would be the equivalent to how some distro packages...

> As a work-around we have to do: > > ``` > cabal get clash-lib-1.8.1 > cd clash-lib-1.8.1 > cabal build --enable-tests --write-ghc-environment-files=always > cabal test > ``` There isn't...

I believe this is a duplicate of #2446 (fixed in git). Please test the latest snapshots.

On October 18, 2023 6:10:28 PM EDT, Lojack ***@***.***> wrote: >@lojack5 commented on this pull request. > > > >> @@ -3,3 +3,4 @@ numpy < 1.17 ; python_version numpy...