On Thursday 12 March 2015 18:07:42 Sune Vuorela wrote:
To the best of my knowledge, the gpu's on the arm platform still are
opengles, not the desktop edition, so while we could build a desktop
opengl qt thing, it would not really be usable in practice.
Right, and glu has never been
Dear Qt/KDE team, Sune,
it seems, that I have the same problem for some other packages.
Libqglviewer was uploaded into experimental, migrating to
Qt5 [1]. It fails unfortunately on armel and armhf and fine on
other archs.
Do you have such a problem for other packages and maybe there is
already
To the best of my knowledge, the gpu's on the arm platform still are opengles,
not the desktop edition, so while we could build a desktop opengl qt thing,
it would not really be usable in practice.
So, my suggestion is to either get the thing ported to opengles upstream, or
disable the package
Hi Sune,
thanks for explanation! I will then request ovito removal
on those archs.
Best regards
Anton
2014-05-21 23:41 GMT+02:00 Sune Vuorela s...@debian.org:
On Wednesday 21 May 2014 13:27:47 Anton Gladky wrote:
Dear Qt/KDE team,
I have some build failures of ovito-package on arm
Dear Qt/KDE team,
I have some build failures of ovito-package on arm platforms [1].
Upstream-author answered, that it is probably due to -opengl es2,
which is set for those archs and ovito requires desktop version
of Qt5.
Are there reasons, why those flags are used for arm platforms?
Thank you
On Wednesday 21 May 2014 13:27:47 Anton Gladky wrote:
Dear Qt/KDE team,
I have some build failures of ovito-package on arm platforms [1].
Upstream-author answered, that it is probably due to -opengl es2,
which is set for those archs and ovito requires desktop version
of Qt5.
Are there
6 matches
Mail list logo
