View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005132||Kali Linux||[All Projects] Feature Requests||public||2018-11-30 07:52||2018-11-30 07:54|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0005132: Ensure Qt can use OpenGL ES drivers for hardware acceleration on arm64|
|Description||Qt offers a build time configuration between using an OpenGL stack or an OpenGL ES stack. In Debian, it uses the OpenGL stack everywhere except on armel and armhf. We would like it to use OpenGL ES on arm64 too because arm64 has many embedded/mobile boards that support only OpenGL ES (either as a hardware restriction or, more frequently, as a restriction of the (proprietary) drivers shipped by the vendor).|
When Qt is built for OpenGL and when the drivers only support OpenGL ES, the user is effectively stuck with no hardware acceleration at all and the 3D rendering falls back to the CPU and it's much slower, leading to a poor desktop experience.
This request has been brought to Debian in the following bug: https://bugs.debian.org/881333
The maintainers seemed to agree and then started a discussion on debian-devel to ensure that the community was in agreement with that change: https://lists.debian.org/debian-devel/2018/11/thrd2.html#00457
In the discussion, they seemed to have changed their mind and will now only do the change if the Debian technical committee believes that it's the best outcome.
At the same time, the discussion showed that it should be not too hard to build two versions of the Qt libraries and it might be that Dmitry Shachnev will implement this. However it's quite clear that it's a poor design decision from Qt to require the user to make that choice at build time and it turns out that for Windows it's possible to make that choice at runtime:
So ideally the best outcome would be to have a similar feature for Linux and with Dmitry we have requested this to the Qt developers through a bug report and a mailing list discussion: