Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14062 > unrolled thread
| Started by | Peter Michael Green <plugwash@debian.org> |
|---|---|
| First post | 2022-04-15 16:30 +0200 |
| Last post | 2022-04-15 16:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
re: PyQt5 question: why are QOpenGLTimeMonitor/QOpenGLTimerQuery not defined on armhf? Peter Michael Green <plugwash@debian.org> - 2022-04-15 16:30 +0200
Re: PyQt5 question: why are QOpenGLTimeMonitor/QOpenGLTimerQuery not defined on armhf? Julian Gilbey <julian@d-and-j.net> - 2022-04-15 16:40 +0200
| From | Peter Michael Green <plugwash@debian.org> |
|---|---|
| Date | 2022-04-15 16:30 +0200 |
| Subject | re: PyQt5 question: why are QOpenGLTimeMonitor/QOpenGLTimerQuery not defined on armhf? |
| Message-ID | <Ecv7r-8VoC-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
> But nowhere do I find any of QT_NO_OPENGL or QT_OPENGL_ES* defined in > the package (but then maybe I'm not looking in the right place? So I > don't know why these two classes are included in the amd64 version of > the package but not the armhf version. The reason is that QT on armel/armhf is built for opengl ES rather than desktop opengl. I believe the reason for this is historic hardware support on armhf systems.
[toc] | [next] | [standalone]
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Date | 2022-04-15 16:40 +0200 |
| Message-ID | <Ecvh7-8Vry-3@gated-at.bofh.it> |
| In reply to | #14062 |
On Fri, Apr 15, 2022 at 03:01:43PM +0100, Peter Michael Green wrote: > But nowhere do I find any of QT_NO_OPENGL or QT_OPENGL_ES* defined in > the package (but then maybe I'm not looking in the right place? So I > don't know why these two classes are included in the amd64 version of > the package but not the armhf version. > > The reason is that QT on armel/armhf is built for opengl ES rather > than desktop opengl. I believe the reason for this is historic > hardware support on armhf systems. Thanks Peter! Best wishes, Julian
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web