Hi Bret! El viernes, 23 de noviembre de 2018 11:14:34 -03 email@example.com escribió: > Just chiming in here as package maintainer of an effected package, OpenMW > and also an upstream developer of said software, along with contributor to > OpenSceneGraph. > > Here are some related open bugs involving Qt and GLESv2 and arm*: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850021 > ^-- RM: openmw [armhf] -- RoQA; needs OSG built against libGL [snip] Yes, that's a drawback we are not hiding. Applications needing Desktop OpenGL would be left out. But... > If you say that arm64 has to be GLESv2 as well, then that is yet another > arch that OpenMW can't be built for. Before the GLESv2 switch, OpenMW > worked just fine on arm* hardware, including the Raspberry Pi/Raspbian with > the VC4 mesa driver that has OpenGL 2.0 support. ...one thing is running and quite another is: how well does it performs when doing 100% CPU-based OpenGL? Are your users *really* interested to use your application when all drawing must be CPU-based? [snip] > I beg you, please either reverse the GLES decision in Qt or provide two > separate packages for GL or GLES support. I'm afraid providing two set ups is a non-go (alas, we would be doing that already and avoiding all this). And I don't there are many armel/armhf users with hardware Desktop OpenGL in their boards.
Description: This is a digitally signed message part.